Develop Bugs

[ROM][IMM76L][4.0.4][AOSP] ICS333 2.0.1 | Team 3xtr3m3 | Fast,stable,easy (6/7/2012)

This ROM is built from Google Android sources, with a few added functionalities programmed by me and others based on CM9 and AOKP to make it more comfortable and user-friendly, improving the user experience.
This is a serious ROM, no functionalities of doubtful utility are added, and their source code is studied in order to be sure what they are exactly doing. This ROM is focused on providing stability and a better stock experience.
{
"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"
}
Main features:
Built from Android sources (IMM76L)
Improved notification bar toggles: long press a toggle to go to related Settings menu; multi-state sound toggle.
Numeric battery indicator (Optional - can be changed to stock battery indicator in Settings -> Battery -> Press Menu Button -> Change battery style).
Brightness control in status and notifications bars (Optional - can be disabled in Settings -> Display -> Brightness control slider).
Real and improved autobrightness: brightness really goes down when light decreases (Optional - Can be disabled in Settings -> Display - Automatic decrease). Based on stratosk's approach but using a logarithmic scale, which fits best to the human eye.
Extended power menu with reboot, recovery and screenshot.
TV-Out (Go to Settings -> Display to activate it).
Video face effects working
Application killing with long press on back button (Optional - Can be disabled in Settings -> Developer options -> Fast application killing).
Choose storage in Camera application
Power button shooter in Camera application
Timer option in Camera application
T9 Dialer
Galaxy S Settings from CM9 are 100% integrated in Settings menu
Removed "R" roaming indicator for national roaming
Root, Busybox and SuperSU
Kernel Semaphore 1.2.2s (387 MB RAM)
HugeMem patch for 720p video by F4K
Preinstalled app: OI File Manager
APN's predefined huge list (source: CM9)
Modified hosts file to remove ads in applications (source: http://winhelp2002.mvps.org/hosts.txt)
What works
Everything!
Known bugs
Camera FC when restoring default settings
Phone app FC if Bluetooth is disconnected while the phone is trying to connect to a Bluetooth headset
**************************************************************************************************
2.0.1 RELEASED!
ALWAYS READ THE FAQ AND SEARCH IN THE THREAD BEFORE ASKING!!!
Download Links
ICS333 2.0.1: http://d-h.st/PpL (Mirror: http://minus.com/mcnldhbFF/)
GAPPS: http://goo.im/gapps/gapps-ics-20120429-signed.zip
If you have questions/problems or you just want to chat about it, you can also go here : http://webchat.freenode.net Channel : ##ICS333
**************************************************************************************************
How to update from a previous version of ICS333:
Flash ICS333-2.0.1-signed.zip in CWM Recovery, without making any kind of wipe
Flash the GAPPS
Reboot. If you have followed these instructions, you won't have lost any data.
If you notice, after updating, that your media (photos, music, videos...) appears twice in Music and Gallery apps, just clear "Media Storage" data (Settings -> Apps -> All -> Media Storage -> Clear data) and reboot. Then, just wait a long while (it can take even 1 hour depending on the amount of media files you have in your phone).
Always check your IMEI after flashing. If it starts with 0049, you have lost your IMEI. If that's your case, read the installation guide for further instructions.
**************************************************************************************************
Clean Installation (if you come from other ROM)
Follow the instructions that are available in this post: http://goo.gl/elAJv (big thanks to psyqiq)
**************************************************************************************************
FAQ
I have flashed the ROM and it works OK, but I can't get signal or make/receive calls/sms. What is happening? You have lost your IMEI. You can get your IMEI back recovering your EFS backup (if you made one) or flashing a Gingrebread Stock ROM (look for one with PDA, PHONE and CSC) with Odin.
I have flashed the ROM and I don't have Play Store. How can I install it? Before flashing, read the instructions! Download the gapps file and flash it.
Does Facebook sync works? No, because adding Facebook sync breaks Picasa sync. The only responsible for this problem is Facebook. You can use third-party apps such as HaxSync for this purpose.
Battery is draining fast. What is happening? Before reporting battery problems complete two charging cycles. If you still have battery problems, ask yourself how long should the battery last with your usage (we are not using an old Nokia phone with 1.0" screen) and discard that is caused by an application. And then, if you still have a draining problem, and you don't know the cause, report your problem attaching:
1) Screenshots of every battery statistics
2) BetterBatteryStats dump. You can download BetterBatteryStats in this thread: http://forum.xda-developers.com/showthread.php?t=1179809. To generate the dump press Menu key -> More -> Dump to File. The dump file will be generated in /sdcard, and its name starts with "BetterBatteryStats".
3) The output of the logcat (the last one better in a private message). In order to get the logcat output, you will have to enable the Logger in the Semaphore app and reboot if you hadn't enabled it before. The logcat starts from scratch each time you reboot or turn on your phone so, wait some hours before sending it.
Remember: just complaining about battery life without providing useful information doesn't help anybody and will not solve your problem.
My music, photos and videos are duplicated in Music and Gallery apps. It usually happens when you flash the ROM without wipe. To fix that, just clear "Media Storage" data (Settings -> Apps -> All -> Media Storage -> Clear data) and reboot. Then, just wait a long while (it can take even 1 hour depending on the amount of media files you have in your phone).
Suddenly, all apps start throwing FCs. What's happening? Your /datadata partition is full. The best solution is to wipe everything and make a clean install of the ROM. Then, when you have finished installing the ROM, flash one of these fixes: http://forum.xda-developers.com/showthread.php?t=1541942, http://forum.xda-developers.com/showthread.php?t=1665742.
Does FM Radio work? Yes, you can download Spirit FM, but do it at your own risk.
Does HW acceleration work when playing videos? Yes, but not with stock player. There are video players in the Play Store that support HW acceleration. For instance, Dice Player.
The LED buttons don't turn on when I have notifications. How can I enable this feature? Download BLN Control from Play Store.
Can I use other kernels such as Devil or MNICS?Yes, just follow their installation instructions as in any other ICS ROM.
Can I customize or remove the toggles of the notification bar? No, you can't But maybe you want to publish a MOD for ICS333?
**************************************************************************************************
2.0.1 changelog:
Updated to IMM76L build
Changed updater script in order to make it harder to lose your IMEI when updating from Gingerbread
2.0 changelog:
New autobrightness system, totally reworked from scratch. Based on the approach of stratosk, but using a logarithmic scale.
Added option for enabling/disabling autobrightness decrease (Settings -> Display -> Autobrightness decrease)
Added option for enabling/disabling "long press on back key to kill apps" (Settings -> Developer options -> Fast application killing)
"Galaxy S Settings" is now totally integrated in the Settings menu.
Updated kernel to Semaphore 1.2.2s (will help with bootloops).
Modified installation script (trying to prevent some IMEI losses, but I can't promise anything).
Updated Messages app: prevents FC when the mmsc is null in the APN.
Updated Email app: prevents wake-ups in downloader component (source: CM9)
Updated translations (thanks to all of you that have collaborated)
Updated Busybox
Updated APN list (source: CM9).
Updated host file (source: http://winhelp2002.mvps.org/hosts.txt)
1.1 changelog:
Added an option to show/hide the brightness control slider of the notifications bar (Go to Settings -> Display -> Brightness control slider).
Added an option to change between stock battery icon and numeric battery icon (Go to Settings -> Battery -> Press Menu Button -> Change battery style).
Tried to prevent an infrequent soft reboot when loading the lock screen.
Older changelogs: http://pastebin.com/3Gbm6uxj
**************************************************************************************************
(Thanks to jarhead166 for the video)
Thanks to:
Huge thanks to Cyanogenmod team for their GalaxyS-specific code, some AOSP modifications and gapps
AOKP team (brightness control and fast application killing)
F4K for the BigMem patch
http://winhelp2002.mvps.org for the hosts file
stratosk for his awesome kernel
psyqiq for his awesome support

This looks promising. Will try it out asap.
Tapatalking in my sleep

Looks really nice, gonna try this soon!

Nice . But GApps link outdated .

btw, where are the AOKP controls? Can't see any controls in the settings menu!!

amirage said:
btw, where are the AOKP controls? Can't see any controls in the settings menu!!
Click to expand...
Click to collapse
Hello! This is not AOKP. The base is AOSP, just took brightness slider and fast application killing from AOKP. Probably I will make these two features configurable from Settings menu in the next release.

Trojan38 said:
Nice . But GApps link outdated .
Click to expand...
Click to collapse
I think that I posted the latest CM9 Gapps package. Check here:
http://wiki.cyanogenmod.com/wiki/Latest_Version#Google_Apps
I don't provide support for other third-party gapps packages.

el_navajita said:
I think that I posted the latest CM9 Gapps package. Check here:
http://wiki.cyanogenmod.com/wiki/Latest_Version#Google_Apps
I don't provide support for other third-party gapps packages.
Click to expand...
Click to collapse
Most updated GApps are always at goo.im : http://goo.im/gapps .

Trojan38 said:
Most updated GApps are always at goo.im : http://goo.im/gapps .
Click to expand...
Click to collapse
Ok, I'll try them to be sure that there is no problem using them and update the post. Thank you!

nice..
do you read my mind?
i also think a simple rom like CM9 but have a Brightness control in status bar like aokp before this and today it is in front of my eye...
i will try it after i go back to my college this friday..

Thanks, look interesting. Will flush it this weekend (so many roms to test!) and report

Trojan38 said:
Most updated GApps are always at goo.im : http://goo.im/gapps .
Click to expand...
Click to collapse
Thank you very much! Link updated.

el_navajita said:
Hello! This is not AOKP. The base is AOSP, just took brightness slider and fast application killing from AOKP. Probably I will make these two features configurable from Settings menu in the next release.
Click to expand...
Click to collapse
Yes you are correct. My mistake. Do you think you could include power saver feature from AOKP in the next update? Would love to have this...it'd be really great.

Thank you el_navajita!!!
Hey, one more new ROM. Flaaaaaaaaaaaaaaaaashing Now. Thank you el_navajita!!!

I will check that feature and think about it. Thanks!
Enviado desde mi GT-I9000 usando Tapatalk

Why not develop clean AOSP ROM odexed 4.0.4 and continue where team ICSSGS stop
Sorry for my english!
Sent from my GT-I9000 using Tapatalk 2 Beta-5

Theoretically, ICSSGS has not stopped. Anyway, this is a very clean AOSP ROM, just with very few additions that I'm sure improve the user experience. It is impossible to build a ROM that likes everybody, you know Anyway, if you want pure AOSP with my ROM, probably replacing some files of my framework with the ones of a stock Nexus S ROM will work.
Enviado desde mi GT-I9000 usando Tapatalk

sorry wrong post
Sent from my GT-I9000 using xda premium

Do you suggest an example?At least, I can see chinese words in websites.
Enviado desde mi GT-I9000 usando Tapatalk

sorry posted in a wrong thread ><
Sent from my GT-I9000 using xda premium

[ROM] SlimKAT [9.0][FINAL] [unofficial] [2015.01.11]

Welcome to SlimRoms SlimKat
Update 1. January 2015
SlimKat 4.4.4 FINAL 9.0
Mirror with all my files incl. NewLayout
This is an UNOFFICIAL build for HTC Endeavoru.
Please report any errors you find. See post 2 for known issues and Special Builds.
Mixed reports for using ART - thanks @oddyZR for this info.
Credits to the people at SlimRoms, that again found new ways to improve the Android experience.
{
"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"
}
Credits and/or respect to people, that refuse to let the HOX die:
audahadi
eyosen
LorD ClockaN
Thömy
Xmister
xzzz9097
VIPER520 & ZhuHang for Viper4Android
EveryoneElseThatDeserveRespect
SlimRoms changelog
SlimRoms gapps
My sources
​
Installation
Requirements: Your device must be unlocked via htcdev.com. There are many guides for this
0)
Make sure your USB drivers are up to date and working. See bottom of this post.
1)
First things first:
Backup your programs/data.
Use your existing recovery to backup your current ROM/Data.
2)
For KitKat you need a new Recovery with SELinux support
Download Thömys CWM6047 or Philz v.6.xx.x-endeavoru or TWRP 2.8.X.X to your PC
Note: You must unzip the image first if you choose Philz. Thomys and mine are ready to flash.
3)
Copy the ROM and gapps to your HOX
Unzip boot.img from the ROM to your PC
4)
Boot to bootloader. Use power button or "adb reboot bootloader"
Flash the new recovery and the boot.img from the ROM.zip
Code:
$ fastboot flash recovery slim-twrp-recovery.img
$ fastboot flash boot boot.img
$ fastboot erase cache
6)
Reboot to recovery.
Clear/wipe data. (You can skip this step if you flash over Slim 3.X)
Flash ROM
Flash gapps (flashing ROM will wipe the system)
Reboot
Please report any issues you find.
Some USB errors in Windows can be solved this way:
Small guide for solving problem with usb not working in Windows.
I never have usb problems with my Linux. It just works. Always.
But at work, my Windows7 like to change settings as it think is best for me. I guess it just don't know me well enough. Here is what I do when Windows get confused and forget what I want.
First make sure you have the latest drivers from Google and HTC.
Install latest drivers from HTC for your PC. http://www.htc.com
Next, get your adb/fastboot drivers updated.
Locate "android.bat", mine is in C:\Android\android-sdk\tools, but yours will be wherever you initially installed your adb drivers.
Run the file and install any suggested updates.
Windows device manager (run devmgmt.msc from start menu or a command window).
Connect your phone and check where it get attached. For a working connection, it should say "Android USB Devices" -> "My HTC", but since you read this, chances are, that your device is in "Other Devices" -> "Android Phone".
That is what this guide will correct.
1. Wrong driver - double click "Android Phone"
2. Update Driver
3. Browse (for your HTC driver, which is already installed)
4. Pick the driver yourself
5. Select "Android USB Devices" -> Next
6. Select "My HTC" -> Next
7. Choose Yes - You know you want the HTC driver
8. Ahhh, success - test your adb/fastboot/MTP/UMS
9. Here is what happened. We make Windows choose the correct driver and Windows will place it under Android USB Devices.
.

Updates & Issues
DL Links below to be updated!
All my files are now at AFH
Updates:
2014.11.07
SlimKat 8.10.2
Change log - please see slimroms.net
2014.10.25
TWRP Recovery 2.8.1.0
Changelog
2014.10.16
SlimKat 8.6.3 with LS-Notification, NetSpeed and BatteryBar
2014.10.15
SlimKat 8.6.1
Changelog: 8.4 + 8.6
Google sign in problems This helped me two times, but other were not that lucky:
Update gsm! Flash com.google.android.gms.zip after flashing gapps.
2014.10.08
TWRP 2.8.0.0 Update
Recovery updated with MTP protocol. This is work in progress with a few quirks.
20140930 SlimKat 8.2
SlimKat 8.2 S - Normal friction (Slow scrolling, like aosp)
SlimKat 8.2 F - Low friction (Fast scrolling)
SlimKat 8.2.4 - Added: LSN + NetSpeedStatus + DTStatusBarToggle + BatteryBar
20140920 SlimKat 8.0.4 Special
SlimKat 8.0 + LSN + NetSpeedStatus + DTStatusBarToggle + BatteryBar
20140919 SlimKat 8.0.3 Special
SlimKat 8.0 + LSN + NetSpeedStatus + DTStatusBarToggle
20140914 8.0 PCFR
Fix/add APNs
Translations
Weekly 7.9 (SlimKat Extra)
Settings: Slimrecents card/text color
Add ADB over network tile
updated apns
more translations
Weekly 7.8 (not build)
Fix Recent Panel defaulting to white on clean flash
External_tinyalsa: Minor updates
Update APN list
Updates translations
20140830 SlimSpecial 7.6
SlimKat 7.6
+ LockScreen Notifications
+ BatteryBar (Top or Bottom)
+ Network Speed Indicator
20140822 SlimKat 7.6
Pure SlimRoms SlimKat
Customise Volume panel - Color it or make it transparent for gaming
Low friction = Fast Scrolling similar to Sense ROMs
20140822 SlimSpecial 7.4
SlimKat 7.4
+ LockScreen Notifications
+ BatteryBar (Top or Bottom)
+ Network Speed Indicator
USB OTG included in kernel (don't know if it actually works) ?
Install from Recovery:
Backup
Wipe Cache
Wipe Dalvik
Wipe System
Flash SlimSpecial
Flash your favorite Gapps
Reboot - Patience, this may take some time
First use may be very slow. Setup new features.
Reboot and let stuff "settle". Should run fine from here.
Optional: Flash kernel from ZIP if you want USB OTG.​
20140816 - SlimKat 7.2.1
More Slim actions.
Recents color and transparency.
Heads up at bottom.
Whether to disable system sounds during quiet hours.
Heads up functionality for messaging.
Added FLAC audio (thanks @Thömy)
Missing: OTG
20140721 - SlimKat 6.6
Changelog: http://www.slimroms.net
Issues: You tell me.
20140721 - SlimKat 6.4
JustArchi build.
Works very well. Only issue I found is GoogleCamera crash if using Lens Blur.
20140719 - SlimKat 6.4
JustArchi + Linaro4.9
Well....:
PlayStore graphics glitches
PowerAmp FC
GoogleCamera crash when rendering Lens Blur.
.
20140710 - SlimKat 6.2
Replaced DSP with V4A
Slims version of Heads Up
Quiet Hours redefined "setup your quiet times exactly like you want"
The rest.
20140703 - SlimKat 6 xtra
Adding Hover and Lock Screen Notifications
Small update to kernel. Might run fine with old kernel though.
2014.06.29
Pure SlimRoms Build 6
WiFi location is back if installing gms-5.0.81
Even better - PlayStore is updated with 5.0.82 - get it there if you can.
Click below for previous SlomRoms
2014.06.22
Back on track. Pure SlimRoms. A few optimisations. Build 5.95
2014.06.15
Installing: Dirty flash shoud be ok, but please flash boot.img!
SlimKat 5.8 - Hover - 2014.06.15
Hotspot fixed.
MMS fixed.
Hover preview.
ART not working.
2014.06.10
SlimKat 5.7 - 4.4.3 - 2014.06.10
Dialer colors partly fixed.
No Hotspot tether.
Mms with small unusable pictures (standard).
Navigation stop working approx 540m before you arrive at work.
Fix for Mms & Hotspot - might even solve Navigation problem as well. Please report if working
Flash boot.img !!! + Flash zip from recovery.
2014.06.09 Dialer colors fixed.
SlimKat 5.7 -4.4.3 - 2014.06.09
This is new android v.4.4.3! Although dirty flash is possible, I highly recommend a fresh install:
Backup your apps.
Create full backup from recovery (in case you want back to 4.4.2)
Wipe system (mandatory)
Wipe data (optional)
Flash ROM and gapps (new gapps available)
2014.06.02
SlimKat 5.6 2014.06.05
Trying to fix network connection problem.
2014.06.02
SlimKat 5.6
Local Build:
- Update tool chain to GCC4.8 for Build and Kernel
SlimRoms:
- Pulse Torch on Incoming calls
- Pimp-up QuickRecord Tile
- Add transparency to Glowpad background
- Shake sensitivity adjustments
Issue:
Very slow or no network connection.
2014.05.22
SlimKat 5.4
- Allow All Widgets On Keyguard
- Add ffmpeg audio&video codecs
- Lots of awesome TRDS updates!!!
- Updated vendor files (TheMuppets)
- Checkout the latest Slim-GAPPS
2014.05.22
Build 5.2a
Fixing bootloop...
2014.05.19
Build 5.2 Shake It more edition.
No dictionary & swype for your language ? --> Here!
Note on hard button lights:
Navigation - HW Buttons
You may have to toggle off/on/off to disable. Try a few times if not turning off first time.
Light is full power Go to /etc/init.d/99_slim_x and edit the last two lines, I use 20. ( min=1, max=255 ):
Code:
echo 20 > /sys/class/leds/button-backlight/button_brightness
chmod 444 /sys/class/leds/button-backlight/button_brightness
2014.05.14
Build 5.1 Shake It edition + New Gapps
Updating from SlimKat:
Boot to bootloader
fastboot flash boot boot.img.
fastboot erase cache
reboot to recovery
(backup if you want)
WIPE/FORMAT SYSTEM - (no need to wipe your data)
WIPE CACHE & DALVIK
Flash the ROM.zip
Flash the latest gapps
Reboot
Enjoy
Coming from other system: You can try procedure above, but if something in system fail do the following:
Backup all your programs and program data
Boot to bootloader
fastboot flash boot boot.img.
fastboot erase cache
reboot to recovery
(backup if you want)
WIPE/FORMAT SYSTEM + WIPE/FORMAT DATA (factory reset, but be careful not to erase your sdcard)
WIPE CACHE & DALVIK
Flash the ROM.zip
Flash the latest gapps
Reboot
Restore your programs & data
Enjoy
2014.05.06
Build 4.9
Included in /etc/init.d/99_slim_x (edit as you want it)
DEFAULT:
Code:
Sweep 2 wake - ON
Direction dependent - YES (Left: off | Right: on)
Distance:400
Button Lights - OFF (almost)
Put # on 4 lines to revert to normal light in buttons
Reboot for changes to take effect.
WiFi location not functional on Googles latest Location Apps.
Found that vol controls BT, if BT is just turned off. Toggle BT on/off may fix it.
2014.04.29
Weekly 4.8
Added config for s2w and button-lights. Edit file /etc/init.d/99_slim_x
2014.04.23
Shake to Secure.
WiFi location not functional on Googles latest Location Apps.
Found that vol controls BT, if BT is just turned off. Toggle BT on/off may fix it.
2014.04.17
SlimKat 4.4 - weekly
Small change to sepolicy in the kernel (boot.img). Not needed for upgrade. To be honest, I don't think it make a big difference. But the logs look better now
2014.04.09
Build 4.2
Fixed low level sound recording on video.
Removed nvidia perfhud, flooding logs.
Lots of small fixes from Slim. Most are for other devices though.
Lost WiFi hotspot again (replaced CM source with AOSP)
2014.04.03 2014.04.02
Build 4.1
Slim updates. Thanks @Iwarsson :good: Sorry - no blue buttons yet
Added experimental code for EAP-SIM. 3 changes at aosp, all marked "Needs Code-Review".
WiFi note: If your wifi gets "locked" (can't turn on or off): Toggle Airplane mode on-off. Should reset wifi-settings error.
This should only happen if you play with SIM settings. Let's see.
NEW GAPPS - AGAIN
d1n0x: Problems connecting with eap. on 04.03 build. Replaced now with "normal" build 2014.04.02
Video recording use wrong microphone, Very low sound.
2014.03.25
Build 3.10
Added code for EAP-SIM/AKA - code is completely untested and still in review at aosp.
Please go to SlimRoms for changelog
GAPPS is updated again 24+25 March. Download at SlimRoms|Downloads|Addons 4.4
2014.03.18
Recents for lefthanded. Resized recents.
GAPPS updated (keyboard error fixed).
2014.03.15
Added camera 16:9 profiles, wide-sizes in Slims source not usable for HOX
Fixed LED notification, thanks Thömy (Flash boot.img for this fix).
Updated audio routing, "it mostly fixes audio input, not the output".
2014.03.11
Build 3.6
A few updates to Browser.
Improvements to Notification Reminder
Improvements to Slim Recents
2014.03.06
Build 3.4
Camera: Some reports of green tint when using flash. Please confirm.
There is no visible notification when headphones is used.
2014.02.28
Build 3.2
2014.02.19
"Stable" Build 3.1 released.
WiFi / BT need testing!
2014.02.11
RC3 released.
SlimPIE, new Dialer, exposed fixes.
2014.02.06RC2 released.
Lots of bug fixes from SlimTeam.
Added support for XposedNote (for history only, not relewant since 9.feb: As Lloir points out there was is a security issue with current implementation.
SELinus are ment to lock down your data, so sneaky apps cannot access it.
This "workaround" to make Xposed work, may let bad behaved modules get to that data.
However this risk was always there in JellyBean and previous releases. It'a all up to you.​2014.02.01WiFi HotSpot​
Not working....
Echo at receiving end ...? Some reports say it is good now
WiFi hotspot
Notification light may blink even without notification ?
Audio distortion ? Uninstall DSP seem to help
Bluetooth works only if wifi is on. Works fine on my phone now. Build 3.2 / Build 3.4
Call: Not able to adjust sound.
​

teemo said:
Not working....
Echo at receiving end? ...... please test
WiFi hotspot.
Click to expand...
Click to collapse
:victory:
Congratz to your new thread! And to a really nice nice rom.
Running it now a couple of hours...and it is as nice as before without the "bugs" it had.
Really BIG Thanks!
No echo bug for me
But WiFi Hotspot unfortunately confirmed not working.

Hey thanks for the rom will try it and add to the OP what this ROM is about and maybe what's the difference between CM and SLIM
Gesendet von meinem One X mit Tapatalk

cappuccina said:
:victory:
Congratz to your new thread! And to a really nice nice rom.
Running it now a couple of hours...and it is as nice as before without the "bugs" it had.
Really BIG Thanks!
No echo bug for me
But WiFi Hotspot unfortunately confirmed not working.
Click to expand...
Click to collapse
Lol no, the echo is not for you - it's for the other part
I had one complain - not sure how reliable though.

Yay! Finally the good cookie has been served.
Downloading.....
Is the "signal drop" bug ironed out?
I didn't have any major complain except that
on past betas.
Will report how it works t'morrow.
Thanks!

Thanks teemo. Good to have slim for hox.

Rowlf said:
Yay! Finally the good cookie has been served.
Downloading.....
Is the "signal drop" bug ironed out?
I didn't have any major complain except that
on past betas.
Will report how it works t'morrow.
Thanks!
Click to expand...
Click to collapse
"Signal drop" should be gone now. But let's give it some time and see.
Actually it was not a signal drop. It was simply the Phone App getting killed. When restarted, it would ask for PIN as it should, which was very annoying.

Impression of first few hours :good:
Initially due to low dpi, I had to use a microscope(almost),
but increased it to 320 everything looks revealing and beautiful.
Everything is working perfectly. ROM is totally smooth and snappy.
A number of annoyances has been reduced/removed.
Battery life(seems to be stable but will decide later).
Upd(04-02-14): The memory leak bug suddenly appeared.
After reboot I tried to turn on bluetooth without turning on wifi
and bluetooth share has stopped error came so I didn't take kmsg.
Bluetooth working fine.
Upd(30-01-14): Battery life seems to be pretty awesome here.
Screen-on time doesn't drain much. And BT is finally working properly.
Greatly relieved that memory leak bug is fixed(hopefully) since the
rom didn't go zero to crap in few hours, unlike other KitKats.
Things to improve(top-medium priority for me) :angel:
- Enable 3-dot menu by default since H/W recent is set to recent apps
(I know I can change recent to menu but 3-dot is convenient)
- Vibration strength should be reduced, currently its causing mini-earthquakes in my room
(Don't know if any option is hidden somewhere, will look for it)
Wishlist(low priority for me) :fingers-crossed:
- Working Wi-Fi tether
- Working Wi-Fi direct(assuming same as CM)
- Theme chooser
Note: My priority is not equal to developer's priority,just expressing my opinion. No pressure, no demands.
Thanks for the great rom. Looking forward to more developments :laugh:

Great I will give it a try tomorrow ! Thank you teemo...

Extremely good work, keep up this great update. Is the most battery friendly rom i have tried after sense. Thanks for keeping the support to hox

Great to see this topic!
Thanks teemo
Sent from my EndeavorU using Tapatalk 2

nice rom , will try it later

Will try this Rom soon , thanks for making it!
Sent from my HTC One X using XDA Premium 4 mobile app

Nice job. Maybe i'll try later, but i need wifi tether for daily use. It's works in CM11.
S2W included or need Trickster Mod? Button backlight notification?

Great job guys, it seems to be very stable.
Just 2 questions....
Is there a way to have profiles?
How get the one shot bouton to erase history of apps?
..sorry for my broken english....
Sent from my Galaxy Nexus using xda app-developers app

Hi teemo thanks for this awesome rom!
Just a question: is it normal that while playing music if I tap on the screen or change task I get sound distortion?

Mat08.cc said:
Hi teemo thanks for this awesome rom!
Just a question: is it normal that while playing music if I tap on the screen or change task I get sound distorsion?
Click to expand...
Click to collapse
Doesn't seem to be normal. I don't have it.
I can go through the menu open app etc without sound problems.
Have you made a full wipe?
Installed a sound mod like v4a?
sent from my slimmed Kitty Kat
---------- Post added at 10:02 AM ---------- Previous post was at 09:58 AM ----------
teemo said:
Lol no, the echo is not for you - it's for the other part
I had one complain - not sure how reliable though.
Click to expand...
Click to collapse
Sure I know that.
It's just after I installed it over 27th build, right after you send me the link I thought I didn't have it (or the other part , I checked myself because I also looked about the phone app crash issue)
But now after full wipe I do have it also unfortunately.
Also tried with xm#16 but still present.
Nevertheless great rom again.
sent from my slimmed Kitty Kat

cappuccina said:
Doesn't seem to be normal. I don't have it.
I can go through the menu open app etc without sound problems.
Have you made a full wipe?
Installed a sound mod like v4a?
sent from my slimmed Kitty Kat
---------- Post added at 10:02 AM ---------- Previous post was at 09:58 AM ----------
Sure I know that.
It's just after I installed it over 27th build, right after you send me the link I thought I didn't have it (or the other part , I checked myself because I also looked about the phone app crash issue)
But now after full wipe I do have it also unfortunately.
Also tried with xm#16 but still present.
Nevertheless great rom again.
sent from my slimmed Kitty Kat
Click to expand...
Click to collapse
I always make a full wipe no sound mods ( I can't even install v4a driver.. ) I noticed that this is happening only with some songs.. it's strange..

Mat08.cc said:
I always make a full wipe no sound mods ( I can't even install v4a driver.. ) I noticed that this is happening only with some songs.. it's strange..
Click to expand...
Click to collapse
Hmm ok.
Maybe try different player?
Haven't tested v4a yet but will do soon...
Edit:
Have you tried latest version? You could also try to disable or unistall dsp manager.
Or of you cannot install drivers because of Super user try a different app.
sent from my slimmed Kitty Kat

[ROM-DISCONTINUED][OPO][6.0.1_r61][AOSP+CAF][CMTE+OMS][MM]CandySiX - Bacon

{
"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"
}
This is CandySiX. Built straight from source with commits from a variety of different Sources/ROMS. We wanted to give the users a fun, fully customizable ROM. We aim to add more features as this project progresses.
Check us out on the web @The-Candy-Shop
@matthew0776 @mar5hal @gimmeitorilltell @Cuzz1369 @rc420head @Flashalot @Venomtester @Darknites @javelinanddart @calebcabob @NoSpamDan
ROM
DEVICE SOURCE
KERNEL SOURCE
Disclaimer: We here at The CandyShop are not responsible for any bricks you may obtain. Please follow the thread rules and steps and everything will be gravy. Remember, backing up before flashing is always recommended.
FEATURES
Choose from CMTE or OMS (RRO Layers is DEPRECATED)
Battery bar
LCD density options
Multi-window
Status bar customization
Quick setting customization
Quick setting pull down options
Force expand notifications
Time contextual headers in panel
Dark UI switch
Advanced power menu
Extra IME options
In-Call vibration options
Lockscreen customizations:
-Shortcuts
-Music visualizer
-Weather​Animations:
-Power menu
-List view
-System
-Toast​Navbar customization (CMTE only):
-SmartBar
-Fling
-Pulse​ Hardware Buttons settings:
-Slim Hardware key rebinding
-Long-press/double-tap actions
-Volume rocker​On the Go mode
Screenshot Crop & Share
Fully charged notification and toggle
CPU info overlay (Developer options)
Snap camera (Sultan's)
More to come, we are never done...
CHANGELOG
Steps:
ATTENTION
Some versions of TWRP, such as 2.8.7.1 have issues flashing radio files, unless you find a version which has this patched. Also, BaNks GApps has announced that they are not supporting TWRP versions older than v3.0.0.0, so It is suggested to use TWRP v3.0.0.0 and up going forward.
You may need to flash a recent CM13 Nightly to get the newest firmware before flashing this.
Coming from another ROM
1) Download CandySiX.zip (See Post #2)
2) Download 6.0 Gapps (optional - See Post #2)
3) Boot into recovery (either twrp or cwm)
4) Full wipe (Dalvik Cache, Cache, System, Factory Data Reset)
5) Flash CandySiX.zip
6) Flash Gapps
7) Reboot
Updating from previous CandySiX release
1) Download CandySiX.zip (See Post #2)
2) Boot into recovery
3) Flash CandySiX.zip
4) Reboot
5) Please give first boot a good few minutes
IMPORTANT - PROBLEMS/ISSUES:
If you have issues, I need the following:
Logs from you (logcat, last_kmsg, dmesg) linked to on pastebin.com or hasteb.in, showing the failure.
A clear description of the steps that I need to take to exactly reproduce the problem.
State what flavor build you are on: CMTE, Layers, OMS, etc...
Please DO NOT complain about problems and offer nothing to help fix it. I reserve the right to ignore you for not following insructions...
NO ETA REQUESTS!
Special thanks to @Cuzz1369, @rc420head, @Sultanxda (CAF kernel), BrokenROM, CyanogenMod, SlimRoms, Omni and all the rest who make their source open. We can't do this on our own.
XDA:DevDB Information
[ROM-DISCONTINUED][OPO][6.0.1_r61][AOSP+CAF][CMTE+OMS][MM]CandySiX - Bacon, ROM for the OnePlus One
Contributors
NoSpamDan, Cuzz1369, rc420head
Source Code: http://github.com/CandyRoms
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
ROM Firmware Required: May need latest CM stable or nightly flashed first if issues...
Based On: AOSP + CAF
Version Information
Status: No Longer Updated
Current Stable Version: 3.2
Stable Release Date: 2016-04-11
Created 2016-01-26
Last Updated 2017-01-05

IMPORTANT: Please understand that if you flash this ROM and experience issues, I need a comprehensive problem description along with logs (logcat and/or dmesg/last_kmsg) of the issue happening.
TWO ROM VERSIONS: Effective 26July2016, choose from CMTE or OMS/Substratum!
(You can NOT flash one on top of the other... If you decide to switch and try the other one, you MUST Clean Flash!)
DOWNLOAD OMS/Substratum themed ROM (Substratum app required - Guide to using Substratum):
CandySiX-bacon-3.2.S-OFFICIAL-0909.zip
DOWNLOAD CMTE (CM Theme Engine based) ROM:
CandySiX-bacon-3.2-OFFICIAL-0908.zip
GAPPS
"Normal" BaNks Dynamic GApps
Open GApps
Recovery:
TWRP v3.0.0 and newer
Extras:
- Flashable DeskClock with updates and fixes to fix the Settings FC.
- If you want to disableCPU underclocking, you can flash @Sultanxda's zip to do this: Disable CPU Underclock.
- If you want to remove the built-in SuperSU, flash this in recovery after the ROM: SuperSU_Root_Remover.zip
Previous ROM versions:
OMS/Substratum base ROMs:
CandySiX-bacon-3.2.S-OFFICIAL-0902.zip
CandySiX-bacon-3.2.S-OFFICIAL-0816.zip
CandySiX-bacon-3.2.S-OFFICIAL-0815.zip
CandySiX-bacon-3.2.S-OFFICIAL-0808.zip
CandySiX-bacon-3.2.S-OFFICIAL-0806.zip
CMTE base ROMs:
CandySiX-bacon-3.2-OFFICIAL-0903.zip
CandySiX-bacon-3.2-OFFICIAL-0820.zip
CandySiX-bacon-3.2-OFFICIAL-0808.zip
CandySiX-bacon-3.2-OFFICIAL-0807.zip
CandySiX-bacon-3.1-OFFICIAL-0729.zip
-----------------------------------------------
Layers base ROMs (DEPRECATED):
CandySiX-bacon-3.1.L-OFFICIAL-0715.zip

FAQ/Info
Due to several requests, here is some further information...
The below touch key and touch key lights disable information is still valid, however I've gotten this integrated into the ROM. The information has been left here for convenience and reference purposes:
DISABLE HARDWARE CAPACITIVE KEYS AND LIGHTS
Several have asked about this. I am working on an in-ROM setting for each, but for now you can do it manually if you like.
If you decide to try/use the following instructions, please understand that you do this entirely at your own risk
Some people like to use the NavBar soft keys (on-screen). If this is you, below you will find some commands you can use to disable the built-in Hardware Keys and Hardware Key Lights.
Using adb or a terminal emulator app (or the built-in one that you can install in your app drawer by enabling Settings > Developer Options > Local terminal), issue the commands under the option you want to apply.
For each item listed, copy/paste or type the commands, one line at a time, and EXACTLY as they are shown. Press ENTER after each command.
Open adb or the terminal emulator app and issue the following commands to start a shell with root access. Press ENTER after each command.
(Be sure to accept any Superuser root access propmpts you receive while doing this.)
Code:
adb shell
su root
Now issue one or a combination of the following:
To DISABLE Hardware Touch KEYS:
Code:
su -c 'echo 0 > /proc/touchpanel/keypad_enable'
To ENABLE Hardware Touch KEYS:
Code:
su -c 'echo 1 > /proc/touchpanel/keypad_enable'
To DISABLE Hardware Touch Key LIGHTS:
Code:
su -c 'echo 0 > /sys/class/leds/button-backlight/max_brightness'
To ENABLE Hardware Touch Key LIGHTS:
Code:
su -c 'echo 255 > /sys/class/leds/button-backlight/max_brightness'
Enjoy!

Reserved
(future use)

oh wow, looks nice. I keep coming back to AOSP based ROM's since they seem to give me the best performance and battery....going to be giving this a go....thanks for the work put in. will report back soon.
Edit: first boot has completed.
had no data upon boot (had cell) so had to go into APN settings and chose the correct APN (fast T-mobile) and change it to IPv4/IPV6 and it connected.
everything else seems to be good other than the fact that I cannot find a place to disable the hardware buttons (i prefer on screen)...did I miss this somewhere?
also, the Default lockscreen clock font is not the default Marshmallow font...its way too bold...and the options lack a "light" font that isn't itallic. I like the options to change this but there needs to be a true marshmallow Default, or at lest a "thin' or better yet, let us add a custom font.
ambient display doesn't seem to be working for me either.

@NoSpamDan Wow.. Great to see candy 6. Can you provide some screenshots?

Let's flash.....
Sent from my A0001 using Tapatalk

layers? wil flash this

Is it AOSP based or CM??

Patience
This is an early beta go-round for me, so please be patient with feature requests. I'm supporting 3 other devices too.
turdbogls said:
oh wow, looks nice. I keep coming back to AOSP based ROM's since they seem to give me the best performance and battery....going to be giving this a go....thanks for the work put in. will report back soon.
Edit: first boot has completed.
had no data upon boot (had cell) so had to go into APN settings and chose the correct APN (fast T-mobile) and change it to IPv4/IPV6 and it connected.
everything else seems to be good other than the fact that I cannot find a place to disable the hardware buttons (i prefer on screen)...did I miss this somewhere?
also, the Default lockscreen clock font is not the default Marshmallow font...its way too bold...and the options lack a "light" font that isn't itallic. I like the options to change this but there needs to be a true marshmallow Default, or at lest a "thin' or better yet, let us add a custom font.
ambient display doesn't seem to be working for me either.
Click to expand...
Click to collapse
Data - Yeah my AT&T APN works out of the box, but if you're on TMO or another carrier, the first thing to do is check APN , which you did.
HW Buttons - Need to look into this further.
Lock screen clock - C'mon look at the options before such reports please. Change it in Settings > Candy interface > Lock Screen > Lock screen clock font options... See the attachments.
Ambient display (Doze) - This may be tricky to track down. Logs would help. Have somone text you or whatnot and log it if Doze is not working. You can try going into Settings > Candy interface > Display and toggle Ambient display off/on or play with the settings there to see if it works? Log this activity too if you can.
pa1281 said:
@NoSpamDan Wow.. Great to see candy 6. Can you provide some screenshots?
Click to expand...
Click to collapse
Of what? Candy has layers and built-in dark mode. That's going to vary widely. See the attachments.
Apayah said:
layers? wil flash this
Click to expand...
Click to collapse
Yes indeed...

rituj26 said:
Is it AOSP based or CM??
Click to expand...
Click to collapse
You tell me... it's in the OP

I can't play any mp3 files. Is that a problem, only me ?

jkmangang said:
I can't play any mp3 files. Is that a problem, only me ?
Click to expand...
Click to collapse
I had this problem on another ROM. What helps is installing v4a

jkmangang said:
I can't play any mp3 files. Is that a problem, only me ?
Click to expand...
Click to collapse
What player are you using? What exactly is failing? Logs please.

PatrickMac said:
I had this problem on another ROM. What helps is installing v4a
Click to expand...
Click to collapse
I just restored my twrp backup of another ROM.
I'll wait for the next release.
---------- Post added at 10:10 PM ---------- Previous post was at 10:07 PM ----------
NoSpamDan said:
What player are you using? What exactly is failing? Logs please.
Click to expand...
Click to collapse
I was using Blackplayer music player. The music didn't start playing.
Then, I thought it might be a problem of my player.
Then, I tried to play it using solid explorer media player. Same problem occurred.
I'll provide the logs later. There was no error shown though.

NoSpamDan said:
This is an early beta go-round for me, so please be patient with feature requests. I'm supporting 3 other devices too.
Lock screen clock - C'mon look at the options before such reports please. Change it in Settings > Candy interface > Lock Screen > Lock screen clock font options... See the attachments.
Ambient display (Doze) - This may be tricky to track down. Logs would help. Have somone text you or whatnot and log it if Doze is not working. You can try going into Settings > Candy interface > Display and toggle Ambient display off/on or play with the settings there to see if it works? Log this activity too if you can.
Click to expand...
Click to collapse
no problem on the requests...understand completely.
as for the lock screen clock, it is st to "default" on boot....and its very Bold, much bolder than stock marshmallow font. I played with the font settings, went back to "default" and it was still too bold. are you seeing the correct font on the defualt setting?
as for "doze", I'll have to get back to you on this. I restored my Nandroid...i just can't live with the hardware buttons. If i have some extra time today I might be able to grab you a log file.
thanks for making this though...i am always on the lookout for AOSP based ROM's.
have you though of making a strict AOSP ROM without any of the add-ons? I know I would be interested in this.

jkmangang said:
I was using Blackplayer music player. The music didn't start playing.
Then, I thought it might be a problem of my player.
Then, I tried to play it using solid explorer media player. Same problem occurred.
I'll provide the logs later. There was no error shown though.
Click to expand...
Click to collapse
I am able to play MP3 files from internal SD using my paid Winamp, but other apps like FX Media Player, Xenoamp, ES Media Player, etc. could not play a test file I tried. Will need to look into this. Not sure if this is codecs or permissions or what.
turdbogls said:
no problem on the requests...understand completely.
as for the lock screen clock, it is st to "default" on boot....and its very Bold, much bolder than stock marshmallow font. I played with the font settings, went back to "default" and it was still too bold. are you seeing the correct font on the defualt setting?
as for "doze", I'll have to get back to you on this. I restored my Nandroid...i just can't live with the hardware buttons. If i have some extra time today I might be able to grab you a log file.
thanks for making this though...i am always on the lookout for AOSP based ROM's.
have you though of making a strict AOSP ROM without any of the add-ons? I know I would be interested in this.
Click to expand...
Click to collapse
I believe I'm seeing the correct lock screen clock font as intended, bold-ish or not. Honestly this is low priority.
As far as HW buttons, I take it you mean disabling them when Navbar is in use? I agree this should be a Navbar option and I'm looking into it.
I'm on a team where a pure AOSP ROM base has been worked on. This ROM is built on the same base, just has some extra features. I'll look at a pure AOSP OPO ROM but I have a lot on my plate right now, and also have no clue how many people would actually be interested in a stripped down vanilla ROM.

Running really good, no reboots, no battery drain.
But there's no live wallpaper support? Can't install KLWP.
Feature request: kill app button would be nice
Keep up the good work!

Tomcar said:
Running really good, no reboots, no battery drain.
But there's no live wallpaper support? Can't install KLWP.
Feature request: kill app button would be nice
Keep up the good work!
Click to expand...
Click to collapse
It's there in the Candy interface > Navigation > Navigation bar > Buttons. If you mean in Recents (which you DON'T really need in M), look in Candy interface > Recents settings. See the attachments.
Getting a little frustrated with the questions here already... I probably should just ignore them but that's not my style...

NoSpamDan said:
...Getting a little frustrated with the questions here already...
Click to expand...
Click to collapse
A lot of OPs of the bacon forums share that frustration. Although personal judgement or a mindset cannot be taught, it doesn't hurt to try a search in Google (or even for features in the Settings app, AOSP added that search button there for a reason!).
My two-cents sorry for OT

[EXPERIMENTAL][AOSP][NRD90U] Unofficial Android 7.0 Nougat build

Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* 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.
*/
Hello guys, this is an unofficial build of AOSP Nougat (with tag android-7.0.0_r6). Kernel is based on CM13's, with some recent commits in kernel/common in AOSP. Sources and patches are available at the end of the post.
Note: this ROM is just for having the first taste of Nougat, and thus missing a lot of key features. I may not be able to update it regularly.
Basic hardware functionality:
Almost everything works, except video hardware encoding, which causes camcorder to fail. HW decoding works though.
Everything should be working since 20160903.
I didn't find more hardware failures, but there can be more.
And remember, the proprietary firmwares and blobs are still in the age of Marshmallow, and a system won't be complete without corresponding firmwares and blobs.
Known bugs:
1. HW disk encryption is likely broken. I reverted some commits to make cryptfs_hw build, but I'm not sure if that works. Do not try it.
2. SELinux is permissive, and init allows service without a SELinux domain to start.
3. GPS may take longer to obtain a position fix. (yes it's working... sorry for the misunderstanding)
4. Only Launcher2 is included. You may install a new one as you like.
5. No LiveDisplay and gestures except DT2W (DT2W can not be turned off via Settings app for now) Color calibration is possible, see FAQ below.
6. Default input method could be broken. Be ready to "pm install your_ime.apk" in adb shell. Fixed in 20160828
7. com.qti.dpmserviceapp may produce continous FC. You can disable it via adb shell ("su -c pm disable com.qti.dpmserviceapp"). Removed in 20160828
8. Rotating screen while playing video can cause the display to "split" Fixed in 20160903
9. Camera service and media codecs all run in the same process, eliminating one of the security enhancements of Android N. May not be fixed until new HAL and blobs are available.
So the security improvements in Nougat are not making much difference in this only-a-taste ROM. If you rely on this, it would be better to wait for official releases.
FAQs:
1. Root / Gapps?
I'm using SuperSU 2.76 stable and OpenGapps 7.0 pico. They work without any issue.
If your contacts / calendars is not syncing, try the following steps:
1. Goto Settings > Apps, tap "Show system" in menu
2. Find "Google Contacts Sync", tap on it, tap "Permissions", turn on everything
3. Go back to Detail screen, clear its data
4. Go back to app list, clear "Contacts Storage"' data
5. Do the same for calendars (2-4)
6. Reboot
Click to expand...
Click to collapse
2. F2FS?
I did not test this myself... But kernel has support already (of cource, it's from CM) so you may have a try. Remember to backup!
EDIT: Some users reported that F2FS partitions are corrupted. If you are using F2FS, maybe you should wait.
Click to expand...
Click to collapse
3. Menu key / App switcher?
Menu key now acts as recents, since I don't think the former is as useful as the latter. And there is no more lag while tapping home button since we don't check for double tap anymore.
Click to expand...
Click to collapse
4. TWRP shows error?
If that's two lines of "log", you can safely ignore it.
If there is something else, please stop and post it here.
If you are using MultiROM, you may modify update-script. Read the first ~8 pages and you will find it.
Reference: I'm using official TWRP 3.0.2 w/o MultiROM This recovery didn't get replaced by stock one...
Click to expand...
Click to collapse
5. File manager (to install APKs)?
http://forum.xda-developers.com/showpost.php?p=68402423&postcount=73
Click to expand...
Click to collapse
6. Disable HW keys, enable soft keys, screen color calibration?
Disable HW keys: echo 0 > /proc/touchpanel/keypad_enable (needs repeat on reboot)
Enable soft keys: echo "qemu.hw.mainkeys=0 >> /system/build.prop (once)
Screen color calibration: echo "32768 31784 27852" > /sys/class/graphics/fb0/rgb (needs repeat on reboot, change the values as you need. This example is 100% R, 97% G, 85% B)
Optionally you can enable color enhancing: echo 1 > /sys/class/graphics/fb0/color_enhance
Click to expand...
Click to collapse
Screenshot spoiler
{
"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"
}
Flashing Guide by @The Dork Knight Rises
In the 3rd post. Direct link: http://forum.xda-developers.com/showpost.php?p=68397804&postcount=3
Video hands-on by @savadam
https://www.youtube.com/watch?v=r54vWk-Azh8
Thanks for all your support!
Download:
20160919: Mirror 1: https://drive.google.com/open?id=0BwkmhbR5VHpAYWRKd1owSUNudEU Mirror 2: https://mega.nz/#!fEk1CTyJ!F8rdnqT_oiipP-tHCuzFGFvsQGmUV6LRaD2t81N2WIA
You can still use HALs from 20160906 if you want.
(And if you are posting this somewhere else, please include the HALs in your post)
Older versions:
20160918: Mirror 1: https://drive.google.com/open?id=0BwkmhbR5VHpAMWZ4OEx6Unp5bU0 Mirror 2: https://mega.nz/#!rdlkgboI!LQuFDtcppbizC_7Tfww1uWAmhw-lYuxjAlrhg9Z0tuQ
20160910: Mirror 1: https://drive.google.com/open?id=0BwkmhbR5VHpAdGVTV3V0ekZaWHM Mirror 2: https://mega.nz/#!XEsTESpR!QDa7he2jdPCeIsbMY1vJAlCZ0RokAKV0IdtyuB0R-yc
20160906: Mirror 1: https://drive.google.com/open?id=0BwkmhbR5VHpAWHNFb0xyYlBZM3c Mirror 2: https://mega.nz/#!zBVX1DTZ!S-LnpIEgJqn1r7So6QmEoD_APUqDnp93XbP-Ug__XBk
CAF and original AOSP HALs: https://drive.google.com/open?id=0BwkmhbR5VHpAaGdCQmxDUWgxQlU
Note on the HALs:
AOSP HALs (msm8996 display + msm8974 media) can not record screen, but they "seem" to make the system smoother. (msm8974 display HAL cannot be used because it corrupts the display when rotating screen with video playing)
CAF HALs (both based on vanilla CAF LA.BF.1.1.3_rb1.13) can record screen but "seem" not to be so efficient as AOSP ones.
The HAL included in the ROM are the AOSP variant.
20160903: Mirror 1: https://drive.google.com/open?id=0BwkmhbR5VHpATlN5T29WTS01Qkk Mirror 2: https://mega.nz/#!OcFlTDDK!EYiNpfE-9Pxx2wu4Oto7kO_oevfe0bMkXOTdhP1HDZc
20160831: Mirror 1: https://drive.google.com/open?id=0BwkmhbR5VHpAVE1WR2xYd180MzA Mirror 2: https://mega.nz/#!jE92iSAD!pl0NMU6PPY3UNXE5DTDBKLUd4sFLG6fNTaUUMI0xdzg
20160828: Mirror 1: https://mega.nz/#!XdlXFDBQ!p7E0N64IEkGHn4GBzOZQDTCgR4KdD00O0dRwJlEnvcw Mirror 2: https://drive.google.com/open?id=0BwkmhbR5VHpAczA2T2g0RUZRS3c
20160827: https://drive.google.com/open?id=0BwkmhbR5VHpAUVdWUHNlc0lHZWs
Note: please read "known bugs" section before flashing! Also you can read the guide below.
When updating the ROM, just dirty-flash new build and Gapps (if you use them).
In order to prevent your recovery from being replaced by the stock one, flash SuperSU along with the ROM.
Sources:
Kernel: https://github.com/updateing/android_kernel_oneplus_msm8974/tree/nougat
Device: https://github.com/updateing/android_device_oneplus_bacon/tree/nougat
Build system: https://github.com/updateing/platform_build/tree/custom-kernel
And there are a lot more repos I didn't fork. The changes there as well as local_manifest are here:
20160918+ Check GitHub
20160910 https://drive.google.com/open?id=0BwkmhbR5VHpAcmo1RjhPd0N1c3c
20160906 No new patches except the HALs. For AOSP HALs, check previous patch archive and Sony's guide. For CAF HALs, just cherry-pick "Fix clang build" from CM.
20160903 https://drive.google.com/open?id=0BwkmhbR5VHpAQXFqZEJCT21UNDA
20160831 https://drive.google.com/open?id=0BwkmhbR5VHpASW54QnR4eGFlR1E
20160828 https://drive.google.com/open?id=0BwkmhbR5VHpAOEx2OWNYcE1xU2s
20160827 https://drive.google.com/open?id=0BwkmhbR5VHpALXdkNkptRnBLMkU
Changelog:
20160919
Fixed Fackbook crash by avoiding preloading libboringssl-compat.so (CM camera HAL is the only camera HAL that does not require this)
Updated BT configuration (please test if it has any side effect. Sometimes you need to search twice to find your Bluetooth gadgets.)
Tried to fix network location (added Google's network location provider)
20160918
Reverted to previous "stub" power HAL. May fix lagging and unusual power consumption noticed by some users.
Tried to fix NFC FW download mechanism. May fix non-working NFC for some users.
20160910
Updated to NRD90U (android-7.0.0_r6)
Switched to CM/QCOM power HAL. The original power HAL is more like a placeholder.
Now on Tap can be launched by long-pressing home button
Switchable WebView implementation, thanks to @fards here
Note:
1. If you are experiencing display issues (such as screen flicker with FLV SW decoding), try switching on "Disable HW Overlay" in Development Settings.
2. If you need multi-user feature, remove /system/priv-app/com.qualcomm.location. Otherwise the system will crash. It was accidentally added in this build.
20160906
Switched back to AOSP HALs to increase performance, but screen recording is broken again. You can choose CAF HALs listed above to fix that. Camcorder and HW encoding work with both variants, no need to worry.
Updated media profiles. Front camera knows that it is not capable of 1080p recording.
20160903
Fixed HW encoder and camcorder (they are different issues, though related) (and switched to CM13 media HAL)
Fixed display corruption while rotating screen with video playing (by switching to CM13 display HAL, don't know which lines of code fixed that)
DT2W can be turned off via Settings
Added Reboot option in power menu
20160831
Fixed crash in World Clock page when selecting countries/regions
Fixed hang in Developer Settings when the ROM is installed as secondary
Fixed crash when taking photos with HDR on
Added support for kexec
Added Stk
20160828
Fixed default input method FC
Remove com.qti.dpmservices to prevent FC
Dev: updated build system to finally automate everything
20160827
Initial build
Click to expand...
Click to collapse
Notes on the sources:
1. Build system produces correct boot.img in $OUT, but the boot image in OTA zip still has no DT included. Fixed in 20160828
2. Some fixes are really "dirty" (as I'm not able to find a proper way)...
3. Some JNIs fail to build (lots of C++ symbols no found). You may try linking C++ libs dynamically (c++_static -> c++_shared) to avoid this. See 20160828 patches, packages/inputmethods/LatinIME for example.
4. Some apps require android-8 ndk, but the earliest version in the tree is android-9. A symlink will do (or you can change the Android.mk in app) but I'm not really sure this will not introduce any bug.
5. Android N split mediaserver into multiple processes to improve security, such as cameraserver, mediacodec, etc. But camera blobs and old HALs were not designed like this. They assume they run in the same process, thus a buffer created by blobs are being used everywhere, which will cause illegal memory access under Android N. I reverted lots of patches about this, forcing camera and codec services to run in the mediaserver process as before - security compromised with functionality, again.
Hope you enjoy this.

I am going to try this out, thanks @updateing for your work:good:
If I could find fixes then I would send an pull request.

The All-In-One Post
Oh look at the time...it's flashy time already? XD
Screenshots:
(Layers themes work. Use Substratum app)
Guide to flashing this properly (TWRP v3.0.2-0):
(THIS GUIDE IS MAINLY FOR THE FIRST BUILD 20160827. AS I AM RUNNING IT SMOOTHLY, I DO NOT PLAN TO UPDATE TO 20160828, AS IT HAS SOME MINOR FIXES, ALREADY COVERED IN MY GUIDE.
IF HOWEVER, YOU'RE FLASHING 20160828 OR LATER BUILD, HERE'S WHAT YOU SHOULD DO DIFFERENTLY:
-Flashing Google keyboard is not mandatory, as default input mode has been fixed
-adb steps do not need to be performed as the com.qti.dpmserviceapp has been removed
-You probably shouldn't flash the SystemUI Tuner mod zip, as the SystemUI APK from previous build may not be compatible with new build. If you flash it on 28 build and have SystemUI FCs or missing SystemUI, just reflash ROM, and don't flash the mod.
REST OF THE GUIDE REMAINS THE SAME)
(This guide is for flashing as primary ROM without MultiROM. MultiROM guide by @7u5h4r: http://forum.xda-developers.com/showpost.php?p=68413163&postcount=242)
TL;DR version (that means short version)
http://forum.xda-developers.com/showpost.php?p=68552389&postcount=1172
Download ROM zip from OP and Google Keyboard flashable zip, as well as any of the zips I linked below.
Wipe your device (data, cache, dalvik/ART cache; preferably even system, just to be as "clean" as possible)
(NOTE ABOUT DIRTY FLASHING:
-If you dirty flash this ROM (eg. flashing newer build), you will need to flash GApps again along with the ROM zip as GApps are not preserved
-This ROM actually booted for me even on a dirty flash from an MM custom ROM, and as a result I didn't face a lot of the problems you'd face on clean flash (GApps crashes, continuous qti app FCs, etc)
But a lot of my apps were crashing until I reinstalled them, and in any case, it is not advised to dirty flash when coming from MM)
Flash ROM zip and keyboard zip, optionally any of the following addons (DO NOT FLASH GAPPS YET):
-SuperSU (v2.68+) for root
-Any of the mods I linked below
-Any other mods like Viper4Android etc (AT YOUR OWN RISK)
Boot into the ROM. you'll probably see a lot of crashes, ignore them, and just find a PC for the next step
(Optionally, you could try to enable Developer Options by tapping past the FC dialogs, once you have DevOps enabled, you'll see an option to mute FC notifications till next boot)
Using ADB on your PC, disable the com.qti.dpmserviceapp package by running following commands:
Code:
adb devices
You should see a device in the list of devices connected
Code:
adb shell
pm disable com.qti.dpmserviceapp
If you get error with permissions, you may need root. If your device is rooted:
Code:
su
pm disable com.qti.dpmserviceapp
(SKIP 6, 7 & 8 if you do not need Google services)
Now reboot into recovery and flash a compatible GApps package (USE 7.0 GAPPS ONLY)
Boot into ROM
Go to Settings>Apps
Find Google Play Services, and go to its Permissions. Enable essential permissions. Now Play Services won't keep crashing on you. Also find Google Contact Sync and give it permission to access Contacts.
Go to Settings>Accounts and add your Google account
Profit
Praise DuARTe
Hit Thanks if this helped
Here's some helpful zips for you guys!
My flashable zip to ENABLE Navbar/softkeys (same as the one on the MM thread) https://drive.google.com/open?id=0B2Y1syM7UNuDYVRhM3BTYVA3SXc
Flashable zip to DISABLE HW keys
https://drive.google.com/open?id=0B2Y1syM7UNuDSFZwUHNLQ0RfdXM
Flashable zip to ENABLE HW keys (revert changes made by zip above)
https://drive.google.com/open?id=0B2Y1syM7UNuDalVLVzd0SFdLekk
Flashable stock bootanimation (same as the one in MM thread; since this ROM doesn't really have a bootanimation and uses the basic fallback bootanimation)
https://drive.google.com/open?id=0B2Y1syM7UNuDelFPZVh6dmxSR2c
Flashable zip to ENABLE Hidden SystemUI Tuner Features (thanks to @AL_IRAQI, see his original guide here)
This one was tricky, my first time decompiling an APK. I was getting some crashes at first, but I think this ZIP should work fine (I tested it on a dirty flash, and it works)
https://drive.google.com/open?id=0B2Y1syM7UNuDd0JBV2ViMXl1bnc
Flashable Google Keyboard 5.1
https://drive.google.com/open?id=0B2Y1syM7UNuDbnBmdEtWZlRlNlk
Flashable Nexus Launcher (credits to uploader)
https://www.androidfilehost.com/?fid=24588232905722237
Replace the stock Power Menu with an extended custom power menu (thanks to @nofx161):
See his post
Link to app
Layers themes are supported, use Substratum app (Play Store link) to apply
(ROOT NEEDED)
NOTE: Themes made only for Substratum will not work (properly) as this ROM doesn't support Substratum (that will need patches to ROM source). Only which support RRO/Layers will work without any issues.

Wow! Great work
Subscribed!

thanks for your work dude

Cool, thanks, gonna try asap
Enviado desde mi A0001 mediante Tapatalk

Great! Thank u dev!

updateing said:
2. SELinux is permissive, and init allows service without a SELinux domain to start.
Click to expand...
Click to collapse
Which sepolicy did you use? I am porting to a different device and Im currently trying to fix neverallows which is painful but I think I merged a commit to qcom/sepolicy which allows domain to start (im not very good in sepolicy). Its based off Cyanogenmod qcom/sepolicy repo. If you want to take a look its here android_device_qcom_sepolicy-1 and I had to add one thing to platform_system_sepolicy. I hope we'll be able to fix sepolicy soon.

Awesome.... Downloading already.

Awesome! Has anyone tried If gapps work?

Flashed it. But i get a FC all the time
com.qti.dpmserviceapp has stopped.
I cant do anything..?

Deltastylez said:
Flashed it. But i get a FC all the time
com.qti.dpmserviceapp has stopped.
I cant do anything..?
Click to expand...
Click to collapse
Really sorry that I forgot this. You could do "pm disable com.qti.dpmserviceapp" in adb shell (su first if it asks so)

A fellow hamster I see! Nice one.

updateing said:
Really sorry that I forgot this. You could do "pm disable com.qti.dpmserviceapp" in adb shell (su first if it asks so)
Click to expand...
Click to collapse
I am kind of a newbie to ADB
Could you perhabs tell me how to? step a step?
Thanks!

Deltastylez said:
I am kind of a newbie to ADB
Could you perhabs tell me how to? step a step?
Thanks!
Click to expand...
Click to collapse
You may find a lot of adb tutorials around...
But if there is a mute option in the FC dialog, you can mute it and disable in Settings.

updateing said:
Really sorry that I forgot this. You could do "pm disable com.qti.dpmserviceapp" in adb shell (su first if it asks so)
Click to expand...
Click to collapse
updateing said:
You may find a lot of adb tutorials around...
But if there is a mute option in the FC dialog, you can mute it and disable in Settings.
Click to expand...
Click to collapse
well, getting this error
" Error: java.lang.SecurityException: Shell cannot change component state for com.qti.dpmserviceapp/null to 2 "
Never mind, fixed

updateing said:
You may find a lot of adb tutorials around...
But if there is a mute option in the FC dialog, you can mute it and disable in Settings.
Click to expand...
Click to collapse
i've tried through adb shell but it doesn't work shell cannot change component state for com.qti.dpmserviceapp/null to 2 moreover it is not possible to disable it in settings thank u for your job

anyone!! please any reviews??

Knew it wouldn't be long before the famous Bacon machine got that great taste of nougat :good:

holy crap holy crap
EVERYONE BOARD THE HYPE TRAIN! CHOO CHOO!

[ROM][UNOFFICIAL][R/A11][F500,LS991,H81x,US991,VS986] /e/ OS | BYE Google, HELLO Privacy!

{
"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.
*/
****
These builds are for all G4 models: official unlocked and UsU'd devices
****
UsU? http://bit.do/unlockg4​
About /e/​/e/ is 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 LineageOS so a very stable base
microG fully pre-installed with Signature Spoofing in restricted mode!
All features described on the /e/ page: What is e
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 CUSTOM?​
F-Droid has been added (The OpenSource alternative store. First search for any apps here!)
Dozens of F-Droid repositories are pre-installed but NOT activated by default (activate them with just a finger tip! That's needed to ensure you only get what you want)
added PhoneSky a patched Google playstore allowing in-app-purchase on microG
added Lawnchair (latest from their TG group)
The above changes are the reasons why my builds are of the type "CUSTOM" and not "UNOFFICIAL".
This is according to the rules /e/ defined.
Known issues​Keep in mind that this is brand new stuff so it may (still) contain unknown issues!
So back up regularly and frequently!
Check the current issues at the github tracker (feel free to help, provide logs etc!)
If you find a bug not listed, follow the instructions here and provide me with the logs: FAQ #1
Requirements​
Your device need to be unlocked either officially (h815 international or h811) or by UsU
Your bootloader stack should be on lastest MM version for your model. That is e.g. 20p for the H815 models or 20x for H811.
So.. NO SUPPORT ON LOWER bootloader stacks then the latest MM version for your model
... and NO SUPPORT for the BETA v29A as well!!
-> for your convenience I have created TWRP flashable files for that !!!! (click)
Of course ensure you just use files for your model, your ARB and UsU'd or not. If unsure ask.
in particular that means this thread is for:
F500, H810, H811, H812, H815 (official unlocked or UsU'd), H819 , LS991, US991, VS986
Latest TWRP - PREVIEW build: click or SHRP build: click
Do a full Nandroid backup before doing anything!
Installation​
This single very first step is for UsU'd devices only (SKIP when you have an official unlocked model):
If you have ever flashed the UsU baseband package: Clean flash the modem partition from your backup in TWRP.
If you do not know if you ever flashed it simply re-flash your modem partition again and you can be sure. This can't do any harm.
If you have no backup:
- TWRP flashable MM modems (N will not work)
Ensure your bootloader is current! You will have issues if you are not on the latest bootloader stack. Read the above Requirements topic to find a link to TWRP flashable files.
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 ????? 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 easy way to have a privacy focused and google-free phone!
Download​
Not available (yet) -> OFFICIAL builds (new install or re-install):
https://doc.e.foundation/search?q=LG G4
CUSTOM builds (new install or re-install):
http://leech.binbash.rocks:8008/e-os/a11
If you have /e/ installed already and just want to update to a newer release:
Android settings -> Updater (yes my CUSTOM builds have OTA support like OFFICIAL has!)
Note:
CUSTOM builds: Builds are updated as soon as possible. There is no fix build cycle.
Information pertaining to your device is displayed accordingly.
The current build is the latest for your device.
Changelogs​
CUSTOM: posted in my Telegram build channel
OFFICIAL: https://gitlab.e.foundation/e/os/releases/-/releases
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​
LineageOS (the base of /e/)
The /e/ foundation and all related devs making this experience possible!
The LG G Four team (aoleary, steadfasterX, Paul Tully)
and more..
Sources
build manifest
e OS source

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 encountered a kernel panic follow FAQ #6 in this post instead.
If you have issues with "just" the boot process follow FAQ #7 for a very easy way to grab the boot logs.
if you have an audio issue follow FAQ #10 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: LIMITED SUPPORT when:
- magisk is installed (known to cause issues sometimes - regardless of the ROM or version)
If you have magisk installed currently UNINSTALL or better do a FULL CLEAN install (see FAQ #2) before doing anything else. Try to re-produce the issue. If it is gone, its magisk related. otherwise 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 with LOS 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 is placed 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: set magisk to 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 Factory Reset and let it do its job
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?
yes this might happen when the following has been solved / implemented (which is NOT the case currently (see known issues):
- selinux = enforcing
- device encryption working
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 #05: It looks like the CPU cores 5 and 6 are disabled - how can I fix that?
TLDR;
There is no fix required! it is fully ok when those are idle. they get hot plugged whenever needed.
Details:
we have 2 clusters of CPU cores resulting in a Hexa-core CPU set: (4x1.4 GHz Cortex-A53 & 2x1.8 GHz Cortex-A57)
the big one (2 CPU cores - higher performance = more battery drain, more heat which potentially causing the: bootloop issue) and the little (4 CPU cores - less battery drain but a bit slower) are handled dynamically based on the load of your device.
the big cluster will run ONLY when it is NEEDED - i.e. high load.
so when you look closer: those are not DISABLED they are IDLE which is a big difference.
Q #06: I get a kernel panic or green/purple/blue screen how to grab logs for this?
When you encounter a kernel panic and you are able to reboot without taking out the battery (taking out the battery will erase RAM and so erase the needed logs):
1) reboot (without taking out the battery!) to either TWRP/SHRP or (if you have root access) to your ROM
2) grab everything need from here: /sys/fs/pstore/ (e.g. adb pull /sys/fs/pstore/)
If you don't have a pc near you can do it directly from the device as well:
Enable the terminal app in developer options or download any
Open the terminal app.
su
cd /sdcard/Download
tar czf pstore.tgz /sys/fs/pstore
Attach pstore.tgz to your post.
It is crucial important that you do this only after the reboot happened . It's not important "when" though - as long as the device stays powered on.
Developers note:
convert PMSG log (requires a linux system):
Code:
tr -cd '\11\12\15\40-\176' < pmsg-ramoops-0 | sed 's/TENS\s/\n/g' > readable-pmsg.txt
Q #07a: I get a kernel panic on boot or having other boot issues but the pstore log are empty! What should I do?
Q #07b: How can I provide a clean boot log?
Since a while there is a very easy way to provide debug logs for the boot process. Before my convenient logging you had to follow FAQ #1 to grab them and it was a bit of PITA for some users.
So here you go for a much easier way:
boot Android
once booted : reboot to TWRP/SHRP
when you have a bootloop instead: take the battery out just before the bootloop occurs, or better press the key combo to get into TWRP all the time to eventually get there directly
once in TWRP ensure that "Cache" is mounted in the "Mount" menu (if not mount it by ticking the box)
open a terminal on your PC and type:
Code:
adb pull /cache/debug/boot_lc_crash.txt
adb pull /cache/debug/boot_lc_full.txt
adb pull /cache/debug/boot_lc_kernel.txt
paste one by one to a paste service like https://del.dog/ , https://paste.systemli.org/ or https://paste.omnirom.org/
Q #8: upgrade your bootloader stack only?! Read here how:
Check the OP of this thread which has TWRP flashable files linked.
Q #9: Is there an /e/ specific FAQ?
Sure:
FAQ: click
Forum: click
HOWTOs: click (a great resource for all your first questions)
Q #10: 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 audo 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 #11: 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.
Q #12: I have graphic glitches / issues, what can I do?
My builds using OpenGL instead of skiaGL since a while. skia is the new and faster renderer coming with pie by default but it can cause graphic glitches in some applications and/or situations.
Is there any fix for skiaGL coming? No, details here .
To check if your current ROM version is using skiaGL do this:
Code:
adb shell getprop debug.hwui.renderer
If you get an empty result or "skiagl" it means skiaGL is active.
If for any reason you wanna enforce skiaGL you can do so by
temporary (immediately activated):
Code:
adb root (must be enabled in dev options)
adb shell setprop debug.hwui.renderer skiagl
or make that change persistent:
Code:
boot TWRP
backup system
mount system
adb shell
echo "debug.hwui.renderer=skiagl" >> /system/build.prop
sync
reboot
.-

I uploaded it, good speed, I will continue to try. Thank you

Thanks for this new ROM
I recommend a full cleanup with format
The only issue I have so far is that I can't connect to my Murena.io account, it keeps on loading. Logs attached

Thanks for this Rom, installed 72 hours ago, feels a bit slower than the same Pie Rom,thats expected, but it is fine, very usable. You do an excellent job with this Rom, feels more fluid and energy efficient than linage pie plus gapps and gms working as it should out of the box, this is the first and only Rom of all, i have tried, in every phone i had since my first android, from 2011 doing that. Wont gonna write nothing about battery usage, or SoT, batteries are the oem LG put in these phones.
Until now the only incovenience is that with dark theme enabled, sometimes, 3 out of 10 times, when i wake the screen its lights wont use the brightness it supposed to use, it wake very dim, i´m still debuging this glitch, pushing the power button to turn it off and then pushing it again bring back to full brightness the screen.

cvmg333 said:
Thanks for this Rom, installed 72 hours ago, feels a bit slower than the same Pie Rom,thats expected, but it is fine, very usable. You do an excellent job with this Rom, feels more fluid and energy efficient than linage pie plus gapps and gms working as it should out of the box, this is the first and only Rom of all, i have tried, in every phone i had since my first android, from 2011 doing that. Wont gonna write nothing about battery usage, or SoT, batteries are the oem LG put in these phones.
Until now the only incovenience is that with dark theme enabled, sometimes, 3 out of 10 times, when i wake the screen its lights wont use the brightness it supposed to use, it wake very dim, i´m still debuging this glitch, pushing the power button to turn it off and then pushing it again bring back to full brightness the screen.
Click to expand...
Click to collapse
The blackout when phone display is off is a well known issue since years with any custom ROM for the g4. We tried to fix that for a long time without any real success.

Interesting note, i did not know about it, thanks for the tip, i will use light theme now onwards then, got another little problem with the microphone, the other person hear me to low, only when i use speakerphone in a whatsapp call, with out the speakerphone activated every thing is working well, have not tried in a normal telephone call yet, i have tried changing microphone volume setting in kernel with ex kernel manager, but no success in that, changing screen colors and saturation works in that app, thank you.

@steadfasterX this could be tried https://github.com/sthomsonpl/devic...mmit/07db7d8be41997765f9a0c60d7e7476b5440545e

I installed this ROM yesterday, and its running fine so far.
Thanks a lot for bringing this gem to ye ole G4.
You really did an excellent job!

Auto rotate not working. H815 UsU'd. Yes - flashed UsU zip.
Edit: Also, when turning on bluetooth, connecting bluetooth headphones then playing a video, bluetooth turns off.
I haven't tested bluetooth on the pie /e/OS or the various LineageOS builds, so it could very well be affecting those too.

Hello,
I have unlocked my G4 H815 EU version with USU and installed /e/-OS with Android 11 on it, but afterwards I noticed that I can't make phone calls. I also can't receive phone calls, but the phone sends a message that I have received a phone call. How could this error be fixed?

pizza_alarm said:
Hello,
I have unlocked my G4 H815 EU version with USU and installed /e/-OS with Android 11 on it, but afterwards I noticed that I can't make phone calls. I also can't receive phone calls, but the phone sends a message that I have received a phone call. How could this error be fixed?
Click to expand...
Click to collapse
flash 20p bootloader stack and modem

Thanks. Where can I find the correct bootloader and modem files?

pizza_alarm said:
Thanks. Where can I find the correct bootloader and modem files?
Click to expand...
Click to collapse
pls check the OP -> Requirements (bootloader stack), Installation (Modem)