Related
Code:
[COLOR="gray"]
/*
* 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 the products you find here before flashing it!
* YOU are choosing to make these modifications.
*/
[/COLOR]
Introduction
- This ROM is for the Apollo and Thor devices only
- Fire Nexus ROM is a refreshed and updated version of the formerly named HDX Nexus ROM.
- It was the first ROM I ever made for the Kindle HDX Tablets
Information + Features
- Pure AOSP Experience
- Open GAPPS nano is built-in
- SuperSU is built-in
- Lean and fast
- Ideal for customisation through Xposed
Prerequisites for Installation
- Safestrap v4 or TWRP recovery
Fresh Installation
- From recovery perform a Factory Reset
- Flash the ROM File
- Reboot and enjoy!
Upgrading to new version
- Flash the ROM File
- Reboot and enjoy!
Downloads
*** Please do NOT create any mirrors ***
- Fire Nexus ROM for APOLLO
- Fire Nexus ROM for THOR
Source Code
- Kernel Source: Kindle HDX stock kernel, build number 1314.4.5.5.1
XDA:DevDB Information
kk-fire-nexus-rom, ROM for the Amazon Kindle Fire HDX 7" & 8.9"
Contributors
ggow
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Version Information
Status: Testing
Created 2016-02-25
Last Updated 2019-10-02
Release Notes / Changelog
17 October 2016
- Ported Google's October 2016 security patches
- Ported Google's September 2016 security patches
13 August 2016
- Ported August 2016 Security Patches
- Ported July 2016 Security Patches
22 June 2016
- June 2016 Security Patch Level
25 May 2016
- May 2016 Security Patch Level
- Added security patch level string to settings app in the "About" page
- Enable swype gestures for Keyboard App
- Fixed keyboard suggestions force closing apps
09 Apr 2016
- April 2016 Security Patch Level
28 Feb 2016
- Switch to using FireOS 4.5.5.1 binaries and boot.img
- TWRP users, dirty update will be fine
- Safestrap users should update to official Amazon FireOS 4.5.5.1, KingRoot, Re-install Safestrap then install ROM.
- Fixed Location Services
- Updated Gapps to open_gapps-arm-4.4-nano-20160228.zip
25 Feb 2016
- Fixed Screen Rotation
- Fixed Proximity Sensor
- Fixed Compass
- Speed up boot time
- Fixed CVE-2015-6602
- Fixed camera picture orientation
- Fixed setting default launcher for latest versions of Google Now Launcher
- Fixed Exchange has Stopped crash on startup
- This may need a fresh install if coming from Nexus ROM 4.0.5
17 Feb 2016
- Initial Release (Fire Phone Only Release)
Reserved
Initial Release
- Dated 25 Feb 2016
- Change log will be on Post #2
- LTE should be working - Can someone please test this on Apollo and Thor
I don't plan on going back to Kit Kat, but thank you!
ggow said:
- Dated 25 Feb 2016
- Change log will be on Post #2
- LTE should be working - Can someone please test this on Apollo and Thor
Click to expand...
Click to collapse
I tried LTE (4G) on my Thor. But it is not working. I found no network provider.
schr01 said:
I tried LTE (4G) on my Thor. But it is not working. I found no network provider.
Click to expand...
Click to collapse
- Try adding an apn
- Also it can take as long as 5 minutes to acquire mobile network
Sent from my Nexus 6 using Tapatalk
Irregular reboots
ggow said:
25 Feb 2016
- Fixed Screen Rotation
- Fixed Proximity Sensor
- Fixed Compass
- Speed up boot time
- Fixed CVE-2015-6602
- Fixed camera picture orientation
- Fixed setting default launcher for latest versions of Google Now Launcher
- Fixed Exchange has Stopped crash on startup
- This may need a fresh install if coming from Nexus ROM 4.0.5
Click to expand...
Click to collapse
On a fresh thor (HDX 7 WiFi) install via Safestrap 4 (coming from Fire OS 4.5.5.1) I experienced a reboot twice so far...
ggow said:
- Try adding an apn
- Also it can take as long as 5 minutes to acquire mobile network
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Sorry I can not use APN. I only know the network provider name (Medion).
But the name does not appear after searching.
schr01 said:
Sorry I can not use APN. I only know the network provider name (Medion).
But the name does not appear after searching.
Click to expand...
Click to collapse
Are you seeing a baseband version in the settings page?
BOFH2k said:
On a fresh thor (HDX 7 WiFi) install via Safestrap 4 (coming from Fire OS 4.5.5.1) I experienced a reboot twice so far...
Click to expand...
Click to collapse
The ROM at the moment is based off 4.5.2, that's probably the reason why your experiencing this. Next update I'll be moving to the FireOS 4.5.5.1.
ggow said:
Are you seeing a baseband version in the settings page?
Click to expand...
Click to collapse
Thanks for the tip with the APN settings. My LTE with ALDI Plus (Eplus) is now working..
Dirty Flash over HDX Nexus v4.0.5
ggow said:
25 Feb 2016
- Fixed Screen Rotation
- Fixed Proximity Sensor
- Fixed Compass
- Speed up boot time
- Fixed CVE-2015-6602
- Fixed camera picture orientation
- Fixed setting default launcher for latest versions of Google Now Launcher
- Fixed Exchange has Stopped crash on startup
- This may need a fresh install if coming from Nexus ROM 4.0.5
Click to expand...
Click to collapse
tl;dr - Dirty flash over HDX Nexus v4.0.5 works (with caveats)
Being the conservative type I held back flashing this release ALAP. Developed a nervous twitch; dog and kids were worried.
My experience:
- starting from a well exercised Nexus v4.0.5 build on an unlocked thor
- above included a handful of Xposed modules and dozens of 'privileged' apps that demand root
- wiped cache/dalvik, dirty flashed 20160225 (nothing else), second cache/dalvik wipe; reboot
- very fast initial start-up (30 sec) followed by several min repopulating caches
- immediately spammed with "process android.process.acore has stopped working" toasts - ugh
- fought way to settings>apps>all and cleared data from Contacts Storage
- messages stopped and everything, including Xposed modules, appears to be working!
- no reauthorizations needed ...
- set animation scales to .75 to match previous responsiveness; may be an artifact of cache rebuild
Still early in testing; will update post as needed. Experience may not apply to Safestrap v4 users (wait for next release)
tl;dr v2: holy-crap-a-saurous!! Never expected it to be this easy. May further delay migration to CM13. Everything just works.
ggow said:
- Dated 25 Feb 2016
- Change log will be on Post #2
- LTE should be working - Can someone please test this on Apollo and Thor
Click to expand...
Click to collapse
FYI - Google location services not working in 20160225 which is a carry over from v4.0.5. Hoping future release can incorporate fix from Fire Nexus ROM for 5th gen devices.
For the curious neither device has a GPS chip in WiFi only models but can obtain an approximate location (often quite good) via Google's location service. The service does work on 3rd gen HDX devices as evidenced by the various CMxx roms.
Davey126 said:
FYI - Google location services not working in 20160225 which is a carry over from v4.0.5. Hoping future release can incorporate fix from Fire Nexus ROM for 5th gen devices.
For the curious neither device has a GPS chip in WiFi only models but can obtain an approximate location (often quite good) via Google's location service. The service does work on 3rd gen HDX devices as evidenced by the various CMxx roms.
Click to expand...
Click to collapse
Location services will be fixed in the next release
Sent from my Nexus 6 using Tapatalk
so, what are the advantages over Nexus ROM 4.0.5 if I may ask?
Anything worth switching to this one until CM 13 is stable enough for daily use (I planned on switching to CM 13 when CM team starts releasing monthly builds and camera is working)?
New Build is Up
- Dated 28 Feb 2016
- Switch to using FireOS 4.5.5.1 binaries and boot.img
- TWRP users, dirty update will be fine
- Safestrap users should update to official Amazon FireOS 4.5.5.1, KingRoot, Re-install Safestrap and then install ROM.
- Fixed Location Services
- Updated Gapps to open_gapps-arm-4.4-nano-20160228.zip
- Change log is also on Post #2
jonashrem said:
so, what are the advantages over Nexus ROM 4.0.5 if I may ask?
Anything worth switching to this one until CM 13 is stable enough for daily use (I planned on switching to CM 13 when CM team starts releasing monthly builds and camera is working)?
Click to expand...
Click to collapse
Assuming you are running 4.0.5 now the primary differences will be in the underpinnings (shared across several devices), ongoing support (v4.0.5 is frozen) and enhancement/fixes introduced over time.
Fwiw - I continue to use HDX Nexus as my daily driver as it is fast, stable and feature complete. Augmented with Nova, Greenify and a few Xposed modules it looks/feels/performs like Android 5/6. I have several devices running CM11/12/13 and occasionally dabble with other flavors such as SlimLP. Some of those roms do hold an advantage on lower resource devices due to optimizations introduced by Google over time. So far nothing has convinced me to switch away from pure, delicious KK in AOSP clothes on a well provisioned HDX.
ggow said:
- Dated 28 Feb 2016
- Switch to using FireOS 4.5.5.1 binaries and boot.img
- TWRP users, dirty update will be fine
- Safestrap users should update to official Amazon FireOS 4.5.5.1, KingRoot, Re-install Safestrap and then install ROM.
- Fixed Location Services
- Updated Gapps to open_gapps-arm-4.4-nano-20160228.zip
- Change log is also on Post #2
Click to expand...
Click to collapse
Confirming Location Services is now working. Woohoo!!
---------- Post added at 11:06 AM ---------- Previous post was at 10:45 AM ----------
Not sure where to post this; will happily move if there is a better location. I wrote about the following behavior in a Nov 2015 post (Nexus 4.0.5). It remains an annoyance as a misfire will immediately FC the foreground app along with any work-in-progress. I was hoping this might magically disappear in more recent builds but it's still there. Thanks in advance for any consideration this warrants; understand it might not be fixable.
On two devices the foreground app FCs if a 'misspelled' word is corrected by selecting a replacement from the ASOP pop-up window. This happens with 100% certainty (app independent; keyboard independent) EXCEPT if the highlighted word begins in the first position of the current input field. Obviously frustrating when near the end of a lengthy input/email/post and loose everything. Of course, the problem can be avoided by disabling the AOSP spell checker under input settings but I prefer to keep it on as: 1) it clearly highlights unrecognized words with a red underscore; and 2) the suggestions are often better than those offered by popular keyboard apps. Note you can display the word list w/o triggering a crash. Just can't select a replacement. Did some reading on this awhile back; has something to do with illegally copying data from an overlay into a foreground window (can't immediately find the reference). Normally one would say it's an app/rom problem but it does not happen on a native Nexus 7. Also wasn't a problem with Nexus v2.
Summary: Foreground app FCs when a replacement is selected from the pop-up list of suggested alternatives when a misspelled word is highlighted (AOSP spell checker).
Davey126 said:
Confirming Location Services is now working. Woohoo!!
---------- Post added at 11:06 AM ---------- Previous post was at 10:45 AM ----------
Not sure where to post this; will happily move if there is a better location. I wrote about the following behavior in a Nov 2015 post (Nexus 4.0.5). It remains an annoyance as a misfire will immediately FC the foreground app along with any work-in-progress. I was hoping this might magically disappear in more recent builds but it's still there. Thanks in advance for any consideration this warrants; understand it might not be fixable.
On two devices the foreground app FCs if a 'misspelled' word is corrected by selecting a replacement from the ASOP pop-up window. This happens with 100% certainty (app independent; keyboard independent) EXCEPT if the highlighted word begins in the first position of the current input field. Obviously frustrating when near the end of a lengthy input/email/post and loose everything. Of course, the problem can be avoided by disabling the AOSP spell checker under input settings but I prefer to keep it on as: 1) it clearly highlights unrecognized words with a red underscore; and 2) the suggestions are often better than those offered by popular keyboard apps. Note you can display the word list w/o triggering a crash. Just can't select a replacement. Did some reading on this awhile back; has something to do with illegally copying data from an overlay into a foreground window (can't immediately find the reference). Normally one would say it's an app/rom problem but it does not happen on a native Nexus 7. Also wasn't a problem with Nexus v2.
Summary: Foreground app FCs when a replacement is selected from the pop-up list of suggested alternatives when a misspelled word is highlighted (AOSP spell checker).
Click to expand...
Click to collapse
- I'll look into this before the next release
Hi,
I am back with one of my builds. Again this is just result of my hobby, feel free to use it, but do it on your own risk. Also any updates will be probably sporadic.
I wanted to publish my build as quickly as possible, becasuse I promised in another thread. So I simply took, what I have (and I am using right now). As a result there some detail I`d like to change for public release like this for the future (e.g. all the special feature enabled by default, the big dmesg buffer). Be careful. I`ll try to do better version as soon as possible. I don`t recomend this for begginers. Be sure you have backup.
This build is based on the official LineageOS code and contains several of my changes. In some cases it could be considered as fix, improvement, but sometimes a hack or even even security risk, so please read carefully following list. All the changes I did because I wanted the system on my device behave that way (at least time to time). Take it or leave it. Please note, that all the features are enabled by default. Be careful.
- built-in root support
- RIL is based on stock KitKat version (works better for me than the official version)
- the sensors libraries are also from stock KitKat (same reason as above )
- barometer sensor is correctly recognized by the system
- the menu button does, what it always did
- notification led brightness can be configured by user
- entering safe mode by holding specific keys during boot can be disabled by setprop persist.safe_mode_disabled true (this has always only annoyed me, but be sure you know you are doing)
- device wakeup by power button can be disabled when proximity and light sensors are blocked (e.g. in a pocket). Execute setprop persist.pwrbtn_proximity_block true
- external sdcard can be made world writeable by setprop persist.world_writable_sdcard true (be careful with this one, this opens a security risk)
- the notification led can blink when the battery is fully charged - enable by setprop persist.blink_when_charged true
- F2FS support
- the notification icons are also on the lock-screen as they ware in
previous Android versions. The carrier name is moved above the clock
(this cannot be turned off)
- the dmesg buffer size is increased to 16M. I set this for debugging
and remove it in next published build.
- ramdisk LZMA compression support
- sdcardfs support - This is faster replacemnt for the FUSE filesystem. I backported this for higher kernel version. Although I`ve been using this for several months without any problem, please consider this experimental. Enable with setprop persist.sys.sdcardfs
force_on
- mount directories for sdcard are protected against writing while the sdcard is not mounted (this solves a race condition problem which allows some apps to create files in there)
- there some other small changes related to my multiboot envrionment, czech translation, carrier name, etc.
Source code
In the installation zip there is a directory code_info with following content:
roomservice.xml - roomservice.xml for the build
commits - list of git repositories and commits used for the build
patches - directory tree with structure reflecting the source and containing
patches for individual projects. The idea (not always followed) is that one patch is one feature,if possible.
code1.diff - all the patches from patches directory together
code2.diff - changes which are not in patches directory
diff-commits.txt - obsolete, I`ll remove this one in the future or maybe use
it again
The only bug I know about is occasional crash of MTP, but I didn`t notice any negative consequences. There may some problem with battery charging (the display turns on time to time without no obvious reason during charging), but it may be some hardware error (bad cable or charger).
Since this is based on official LineageOS, thanks to everyone who contributed to it.
I am using this build for over a week without any problem, except those mentioned above.
Continue here, for the latest build.
UPDATE:
I totally forget about this yesterday - here are the proprietary files I used for this build proprietary-files-ocm13-skk-ril.tgz It is a mixture from the CM 13 official build and KitKat stock files, with modified ks file (then connect symbol is replaced with xonnect, so it doesn`t crash), maybe some other files and changes. I really don`t remember, I put this together during a long period of time. If you find any of your work inside, please accept my apologies and let me know. From my point of view it just works. If you want to apply the patches, then you will most probably want to change the hardcoded full path to these files in device/samsung/i9305/extract-files.sh.
UPDATE:
If you want to use anything from my patches, feel free to do so, just follow the license of the original project.
I tested it for about 4 hours for modem stability, taking the logs. All SAHARA transfers were ok, with no errors and retries. I should have mentioned your name in some post earlier
gongrats and many thanks @p.a.n. Your rom runs very well, its awesome. :good:
Do you mind, if I take your sources or parts of it or some files from your rom.zip for my builds? If I do so, I will mention you and what I took and give you credits.
rodman01 said:
gongrats and many thanks @p.a.n. Your rom runs very well, its awesome. :good:
Do you mind, if I take your sources or parts of it or some files from your rom.zip for my builds? If I do so, I will mention you and what I took and give you credits.
Click to expand...
Click to collapse
Thanks Use whatever you want from it just follow the license of the original project (I updated OP with similar note).
Help??? How to fix gps on this Rom plzz
Great work p.a.n.
Using for 24 hours no problems yet and seems very smooth.
Used it for a few hours with the built-in kernel then switched to Boeffla to get Boeffla Sound etc.
Very nice to have the customisable LED again as it was missing from the official LineageOS.
More importantly for me, the magnetic compass seems to work properly. I couldn't get it to work on official, nor on Rodman's RR.
No issues with GPS for me.
I had to install 'The SELinux Toggler' to set permissive so I could get Viper4Android to work (as with official) but I expected that.
One other thing, the MTP crash is the 'MTP host' app. I just disable this as it's only needed if you need your phone to be an MTP host for something like a digital camera, which I don't. It doesn't affect connections to your PC.
Is there an issue with the automatic execution of init.d scripts? I'm on Boeffla so it may just be that. Luckily you can tell Boeffla app to execute them anyway.
@Glenn2, thanks for testing I am not completely sure about it, but if I remember well, the compass problem is caused by the opensource sensor library (I think that just replacing the/system/lib/hw/sensors.smdk4x12.so with the one from my build should fix that). But the problem is not actually with the compass sensor, that one is ok, but in the opensource version there are missing some "fake" sensors, which provide calculated data based other "real" sensors. One of them provides orientation information, often used in apps as compass. Try some app (e.g. Androsens2) which lists all the sensors and you`ll see the difference - the "fake" ones have iNemo in their name.
I actually don`t care about the MTP crashes. It mostly happens after uninstalling some app, which doesn`t happen too often and otherwise I haven`t noticed any negative related to that. It is just annoying popup for me.
What do you mean by the question about init.d scripts?
p.a.n said:
What do you mean by the question about init.d scripts?
Click to expand...
Click to collapse
I have a couple of scripts and they were not running on boot. I don't know if Boeffla kernel affects busybox. I remedied this by telling the Boeffla Config app to run init.d scripts when it launches.
Also, I had a power manager service wakelock that kept my phone awake for hours, only a reboot cleared it. I had this happen a couple of times on official LineageOS too. Not the famous mdm_hsic_pm0 which now seems to be cured at long last! I had a period of no signal when I was on the London Underground, maybe that was the cause.
Glenn2 said:
I have a couple of scripts and they were not running on boot. I don't know if Boeffla kernel affects busybox. I remedied this by telling the Boeffla Config app to run init.d scripts when it launches.
Click to expand...
Click to collapse
There is /system/etc/init.d/* scripts, which run OK, or at least /system/etc/init.d/00banner does. There is also /system/etc/init.d/90userinit, which executes /data/local/userinit.sh. I remember that seme previous CM version there was also a user defined init.d somewhere in /data. This may what has changed, but I am not if this is your case.
Glenn2 said:
Also, I had a power manager service wakelock that kept my phone awake for hours, only a reboot cleared it.
Click to expand...
Click to collapse
This on is also often on the top of my kernel wakelock list, but never that bad, always with reasonable times.
Glenn2 said:
Not the famous mdm_hsic_pm0 which now seems to be cured at long last!
Click to expand...
Click to collapse
Yes, the solution has been sitting in the Samsung kernel source for a long time ...
Glenn2 said:
Great work p.a.n.
Using for 24 hours no problems yet and seems very smooth.
Used it for a few hours with the built-in kernel then switched to Boeffla to get Boeffla Sound etc.
Very nice to have the customisable LED again as it was missing from the official LineageOS.
More importantly for me, the magnetic compass seems to work properly. I couldn't get it to work on official, nor on Rodman's RR.
No issues with GPS for me.
I had to install 'The SELinux Toggler' to set permissive so I could get Viper4Android to work (as with official) but I expected that.
Click to expand...
Click to collapse
Do you install the last rom ??? Or not
It is worth pointing out that after backing and restoring between roms, the SELinux attributes for efs files can become not correct. That can lead to something like this :
Code:
06-28 04:17:43.705 3799 3799 W ks : type=1400 audit(0.0:30): avc: denied { read } for name="efs1.bin" dev=mmcblk0p11 ino=8200 scontext=u:r:qcks:s0 tcontext=u:object_r:unlabeled:s0 tclass=file permissive=0
Code:
06-28 04:17:43.712 3799 3799 E kickstart: Requested ID 16, file "/tombstones/qcks/efs1.bin"
06-28 04:17:43.712 3799 3799 E kickstart: ERROR: function: open_file:80 Unable to open input file /tombstones/qcks/efs1.bin. Error 13: Permission denied
It results in not working RIL because of enforced SELinux. Running restorecon fixes the problem.
moad gastro said:
Do you install the last rom ??? Or not
Click to expand...
Click to collapse
I don't know what your question means, as there is only one ROM. I installed from the link in the OP (dated the same date as the OP).
Still using this ROM, and still very few problems.
The day before yesterday it crashed with the screen off. Had to hold power button in to restart.
And yesterday the damn wakelock. It got stuck at a time when I had no signal, and also I used the camera, so either may be relevant. It didn't seem to cause any drastic battery drain though (see images attached). I suppose when the CPU is awake but only at 200MHz and not doing much it uses little more than when it is sleeping?
Regarding init.d scripts. I added one to /system/etc/init.d that simply writes a file to /data when it runs, to test that it DID run. Script starts #!/system/bin/sh
Results:
1) rom with its own kernel - didn't run
2) rom with Boeffla kernel - didn't run
3) rom with Boeffla kernel and Boeffla Config app set to execute init.d scripts itself - did run
One more, just for fun!
Two days ago I was at the Wimbledon tennis, and the location service and/or weather widget decided I was in Boulogne-Billancourt (Paris) instead! I then opened and closed Maps, refreshed the widget and it changed to the correct location!
..
Hi,
I'm trying to install the current build using TWRP 3.0.2-1, but it gets stuck at the "Patching system image unconditionally..." step with the progressbar at around 40%. It's been sitting there for about 10 minutes. Does anyone know how that'd be fixable?`
Cheers
Latest build is ok for me. I've flashed it using TWRP 3.1.0 build from rgib
https://drive.google.com/drive/folders/0B7pwslEEF0l4Yzk2Nm1jOGRDQVU
{
"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"
}
ABOUT:
CarbonROM is an aftermarket firmware based on the Android Open Source Project created with the purpose of adding versatility and customization to stock Android. Stability is our highest priority; our vision is to be the best alternative to a stock operating system for your device.
WHAT'S WORKING:
- All core features:
- Hotspot
- IR blaster
- Reading mode
- GPS (locks in 2 minutes)
- Goodix fingrprint (needs another verification)
- VoLTE
- LTE (speed reaches 50 MB/s)
- Agressive battery modes ( 3 versions - idle, standby, battery saver)
- umatched stability and INSANE battery life - second to none
- clean, lean and efficient
KNOWN ISSUES
- Nothing found
- You can report to this email address
SELinux Status Enforcing
SCREENSHOTS
CLEAN FLASH RECOMMENDED
Back Up Everything.
Use Orangefox Recovery. Link
Wipe Dalvik/ART cache, Cache, System, Data.
Flash ROM
Flash Gapps. (FlameGapps Recommended)
To update the ROM, you can use two methods - OTA or Dirty Flash. OTA is recommended.
DOWNLOAD:
CARBON CR8 RELEASES - MIDO
TEAM WEBPAGE: CarbonROM
TELEGRAM: CarbonROM
Support the efforts of the team: Donate
Version Information
ROM OS Version: Android 10.0.0
ROM Kernel: Linux 3.18 - KERNEL Repository
Status: Stable
Stable Release Date: 2021-04-20
Finally published on XDA, a very good ROM, I use it on a daily basis,screen 9+ hours, the speed is at the level of PE 9 CAF, who needs lightweight ROM, with the latest security patches, and without bugs, I can recommend Carbon
Solid ROM. I chose it thanks to the Kill option in the Recents task switcher.
Note that unlike LineageOS, CarbonROM doesn't come with a built-in firewall since contemporary android (last year or so) lets you use rootless firewalls via vpn redirects. Personally I've rooted and used afwall regardless since I need root for adaway.
Mi Remote works fine in case you're wondering. You don't need to allow any permissions and can even firewall it after "pairing" your TVs and it will still work.
One question/caveat: How do I enable lock screen rotation?
~ Redmi Note 4X 64GB
xdaluser0 said:
Solid ROM. I chose it thanks to the Kill option in the Recents task switcher.
Note that unlike LineageOS, CarbonROM doesn't come with a built-in firewall since contemporary android (last year or so) lets you use rootless firewalls via vpn redirects. Personally I've rooted and used afwall regardless since I need root for adaway.
Mi Remote works fine in case you're wondering. You don't need to allow any permissions and can even firewall it after "pairing" your TVs and it will still work.
One question/caveat: How do I enable lock screen rotation?
~ Redmi Note 4X 64GB
Click to expand...
Click to collapse
To be honest, I do not really know if this is possible.
The lock screen normally shuts down most of the censors.
If you are sure that the accelerometer is active when the screen is locked, it has to be researched.
Otherwise, you would need TYPE_MAGNETIC_FIELD and TYPE_ACCELEROMETER to adjust the settings.
I, personally, don't think it is possible.
Per5on said:
To be honest, I do not really know if this is possible.
The lock screen normally shuts down most of the censors.
If you are sure that the accelerometer is active when the screen is locked, it has to be researched.
Otherwise, you would need TYPE_MAGNETIC_FIELD and TYPE_ACCELEROMETER to adjust the settings.
I, personally, don't think it is possible.
Click to expand...
Click to collapse
Thanks for replying. I'm asking because it's fairly common in other ROMs so I assumed the setting was buried somewhere in the menus. I even looked it up over the github repos ( https://github.com/search?q=org:CarbonROM+lock+screen+rotation&type=commits ) and found multiple commits suggesting it's an existing feature: https://github.com/CarbonROM/android_frameworks_base/commit/afc54cf30f9c3adb4038dc3363cf47bbefc01564
sdm660-common: overlay: enable lock screen rotation · CarbonROM/[email protected]
Contribute to CarbonROM/android_device_xiaomi_sdm660-common development by creating an account on GitHub.
github.com
Sensors wise, I think that's the sleep mode that cutoffs those circuits rather than the lock screen itself so once the display turns back on the sensors are back on as well. But that's just me making guesses really.
Ok I managed to get the lockscreen rotating but it isn't easy. Basically you need to add a line to build.props using magisk's MagiskHide Props Config module. So, from the terminal after installing and rebooting you su and run props which is a menu driven terminal script. You add a new one (I think it was no.4 in the menu? follow the on-screen instructions...) called lockscreen.rot_override and give it the value true. Then let props initiate the reboot and you're done.
TL;DR lockscreen.rot_override=true in build.props
Anyhow, would have been nicer to have it as a CarbonFiber but so long as it works, I'm not complaining Thanks.
Another day another odd bug / missing feature: It's likely at least two-three separate su (magisk) and missing permissions possibly related to the new Android privacy polices, but Automation / Easer / Automate / LibreTasks can't use the wifi as a trigger due to missing permissions. E.g. previously I'd use LineageOS's System Profiles to turn off mobile data when my home wifi was connected but now nothing can list the wifi networks (related permissions maybe?) or switch off mobile data (su / magisk root elevation by the service probably needs work on the app dev's side) but third party tools are all broken for various reasons.
Anyhow, It's probably not ROM related but since LineageOS circumvents the issue by providing their own, I think it's still a valid point of comparison especially for people that consider event driven automation as necessary. Personally I guess I'll just try and remember to turn it on/off.
p.s. Links of what I've tested not to work:
Automate - Apps on Google Play
Automate almost any task on your device
play.google.com
Easer | F-Droid - Free and Open Source Android App Repository
Event-driven Android automation
f-droid.org
Automation | F-Droid - Free and Open Source Android App Repository
Automate stuff on your device by creating rules.
f-droid.org
LibreTasks | F-Droid - Free and Open Source Android App Repository
Trigger actions when certain events happen
f-droid.org
xdaluser0 said:
Another day another odd bug / missing feature: It's likely at least two-three separate su (magisk) and missing permissions possibly related to the new Android privacy polices, but Automation / Easer / Automate / LibreTasks can't use the wifi as a trigger due to missing permissions. E.g. previously I'd use LineageOS's System Profiles to turn off mobile data when my home wifi was connected but now nothing can list the wifi networks (related permissions maybe?) or switch off mobile data (su / magisk root elevation by the service probably needs work on the app dev's side) but third party tools are all broken for various reasons.
Anyhow, It's probably not ROM related but since LineageOS circumvents the issue by providing their own, I think it's still a valid point of comparison especially for people that consider event driven automation as necessary. Personally I guess I'll just try and remember to turn it on/off.
p.s. Links of what I've tested not to work:
Automate - Apps on Google Play
Automate almost any task on your device
play.google.com
Easer | F-Droid - Free and Open Source Android App Repository
Event-driven Android automation
f-droid.org
Automation | F-Droid - Free and Open Source Android App Repository
Automate stuff on your device by creating rules.
f-droid.org
LibreTasks | F-Droid - Free and Open Source Android App Repository
Trigger actions when certain events happen
f-droid.org
Click to expand...
Click to collapse
If you want to inform the team, you can use the email address in the description.
As to automation, normally when you have both LTE and Wi-Fi connected, the connection is set to sign in to the closest cell, irreleveant of the technology used. The distance marks ping times, strength of signal, velocity but even when it connects, you still have the both sensors active (which drains battery). Currently, I don't think there is a way to automatically shut down one of them, or both of them, if this is what you mean.
In terms of selection of the network, it has always worked. In terms of dozing the sensors after a certain time of inactivity, I cannot help you.
Hopefully, this is useful.
Per5on said:
If you want to inform the team, you can use the email address in the description.
Click to expand...
Click to collapse
Nah it looks like the automation stuff is being shifted into the assistant APIs and SDKs and most projects and foss just hasn't caught up with the changing permissions and such: https://www.xda-developers.com/android-10-rules-automation-feature-rolls-out-some-pixel-devices/
Per5on said:
Currently, I don't think there is a way to automatically shut down one of them, or both of them, if this is what you mean.
Click to expand...
Click to collapse
I guess google wants their machine learning to do this automatically for users instead of the users having to go into the settings and script logic.
Anyhow, I'm sure things will sort themselves out with time so no worries.
Offtopic, for some reason Axet's Call Recorder didn't work for me even after giving it root so I had to use the magisk module that installs it as a system app. It's sorta weird since android.permission.CAPTURE_AUDIO_OUTPUT should have been granted as I checked "System Mixer Incall Recording" and approved it for superuser but it didn't. I even thought something went wrong with magisk itself but adaway and afwall test fine so...
Anyhow, thought it's worth mentioning since I keep running into similar premission related issues and some of them are common enough that people already have apps to solve/circumvent them.
Changelog - 20/04/2021
Hello!
I've switched to this ROM because android 11 and kernel 4.9 was not stable for me, with all kind of slowness and issues.
I'm glad to see an up-to-date android 10 rom. The performance is just insane compared with the other rom's i've tested.
But I do experience a bug with wireless. When my phone is connected to a 2.4ghz wifi AP, the performance is really low, below 4mbps with high jitter, even with the signal at 100%. If I connect to the 5ghz band, the performance is perfect, above 115mbps.
How can I help you with troubleshooting this? Unfortunately this is a massive problem for me. Changing wifi channels and 20 or 40mhz bandwidth makes no difference at all.
TigTex said:
Hello!
I've switched to this ROM because android 11 and kernel 4.9 was not stable for me, with all kind of slowness and issues.
I'm glad to see an up-to-date android 10 rom. The performance is just insane compared with the other rom's i've tested.
But I do experience a bug with wireless. When my phone is connected to a 2.4ghz wifi AP, the performance is really low, below 4mbps with high jitter, even with the signal at 100%. If I connect to the 5ghz band, the performance is perfect, above 115mbps.
How can I help you with troubleshooting this? Unfortunately this is a massive problem for me. Changing wifi channels and 20 or 40mhz bandwidth makes no difference at all.
Click to expand...
Click to collapse
Hi!
First, I have none of your issues and have no information on anyone else experiencing it.
If you connect to 2,4 Ghz, the range is longer and wider, which means the strength and velocity is somewhat disturbed by the distance from the router or the AP, but ensures longer distance. Drops are fewer than in the 5 GHz.
If you use 5 Ghz, it is much more stable but the distance is shorter and the channel is narrow, which leads to easy disturbance of the connection.
If you use the Hotspot for someone close to you (not far than 5-7 metres) use the 5 GHz.
Changing the bandwidth of the channel might improve something but rather not.
If you have any other questions, do not hesitate.
Thank you for your answer but unfortunately I do experience this problem with this ROM and not with others
I'm aware how wifi networks works but where I'm mostly using my device, I don't have 5ghz available.
I need proper 2.4ghz stability because I use ms teams on my device for home office.
This problem is not present with other android 10 roms with kernel 3.18 like lineage os.
Let me know if you need logcats or anything
Per5on said:
View attachment 5265955
ABOUT:
CarbonROM is an aftermarket firmware based on the Android Open Source Project created with the purpose of adding versatility and customization to stock Android. Stability is our highest priority; our vision is to be the best alternative to a stock operating system for your device.
WHAT'S WORKING:
- All core features:
- Hotspot
- IR blaster
- Reading mode
- GPS (locks in 2 minutes)
- Goodix fingrprint (needs another verification)
- VoLTE
- LTE (speed reaches 50 MB/s)
- Agressive battery modes ( 3 versions - idle, standby, battery saver)
- umatched stability and INSANE battery life - second to none
- clean, lean and efficient
KNOWN ISSUES
- Nothing found
- You can report to this email address
SELinux Status Enforcing
SCREENSHOTS
View attachment 5265947View attachment 5265953
CLEAN FLASH RECOMMENDED
Back Up Everything.
Use Organefox Recovery. Link
Wipe Dalvik/ART cache, Cache, System, Data.
Flash ROM
Flash Gapps. (NikGapps Basic Recommended)
To update the ROM, you can use two methods - OTA or Dirty Flash. OTA is recommended.
DOWNLOAD:
CARBON CR8 RELEASES - MIDO
TEAM WEBPAGE: CarbonROM
TELEGRAM: CarbonROM
Support the efforts of the team: Donate
Version Information
ROM OS Version: Android 10.0.0
ROM Kernel: Linux 3.18 - KERNEL Repository
Status: Stable
Stable Release Date: 2021-04-20
Click to expand...
Click to collapse
This looks like a good rom. I will test it on my device.
TigTex said:
o Thank you for your answer but unfortunately I do experience this problem with this ROM and not with others
I'm aware how wifi networks works but where I'm mostly using my device, I don't have 5ghz available.
I need proper 2.4ghz stability because I use ms teams on my device for home office.
This problem is not present with other android 10 roms with kernel 3.18 like lineage os.
Let me know if you need logcats or anything
Click to expand...
Click to collapse
Ok, send them to me. I will take a look when I have some time to do so.
No promises.
I found the problem it's bluetooth.
I have a mi band that is always connected to my device. Just by having bluetooth enabled, I can't have more than 4mbps. Disabling it, I can use wifi happily at 70mbps.
Is there a bluetooth coexistence mode that can be tweaked?
TigTex said:
I found the problem it's bluetooth.
I have a mi band that is always connected to my device. Just by having bluetooth enabled, I can't have more than 4mbps. Disabling it, I can use wifi happily at 70mbps.
Is there a bluetooth coexistence mode that can be tweaked?
Click to expand...
Click to collapse
They are on the same chip
Check here
I'm aware of it. But like I said, this was a non-issue with miui and LOS17.1.
Perhaps there's a tweak on WCNSS_qcom_cfg.ini that can be done? Or maybe los17.1 uses different blobs? You could try to push zeelogs 17.1 kernel to cr-8.0.
These are just ideas, not complaints
TigTex said:
I'm aware of it. But like I said, this was a non-issue with miui and LOS17.1.
Perhaps there's a tweak on WCNSS_qcom_cfg.ini that can be done? Or maybe los17.1 uses different blobs? You could try to push zeelogs 17.1 kernel to cr-8.0.
These are just ideas, not complaints
Click to expand...
Click to collapse
Good suggestions!
you can send them to the email address in the description
Great rom!!! Very stable in my 3/32 mido. Good battery backup so far.
A bug I found - google assistant is not working and it's showing 'not available in this device'.. Is there any way to fix it??
Code:
/*
* 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.
*
*/
Hi,
here you can find my version of LineageOS 20.0 for our Samsung Galaxy Note 2 (3G).
At first I want to thank @rINanDO, @ChronoMonochrome for all your work on these devices!
This is an alpha version, it's not finished from the LineageOS side and also not from mine.
Most of the LineageOS specific features are missing or not working yet,
please do not report bugs.
Attention:
As it looks like does the device stuck at the "Samsung Note II" screen when you boot out of TWRP,
simply touch the screen with your fingers and it will move on...
I try to find out whats going on there
If you wan't to enable the back gesture for gesture navigation, do the following:
adb shell
setprop toggle_navbar true
You can do the same to disable it.
Here you can see how far everything is working for now.
Spoiler: Whats working
Boot
Audio
Bluetooth
Graphics
Cameras
Sensors
Wifi
GPS
USB
Video playback (HW/SW)
Tethering via USB
RIL
OTA-Updates
Tethering via WIFI and Bluetooth
much more...
Spoiler: Whats not working
NFC
Encryption
BT audio in a phone call
Network monitoring because of missing eBPF
Maybe random reboots
Spoiler: Links
TWRP
ROM direct link
ROM Android-Filehost
ROM Mega
Spoiler: Changelog
29.09.2022
17.10.2022
26.01.2023
10.03.2023
Spoiler: How to improve GPS
You could use a gps.conf from https://app.box.com/s/w57s1v1n3hie7l5lk28i for your location and replace /system/etc/gps.conf.
Or you try GPS Server Optimizer app for a faster 3D fix.
For both methods you need root rights.
I would recommend to use microG instead of BitGapps,
here you can find the installation instructions:
Spoiler: microG instructions
Download Magisk 24.1 and flash it via TWRP (yes, flash the APK file), reboot
Open Magisk and update the App (and do a reboot if it's asking)
Enable Zygisk in Magisk
Download and install microG installer in the Magisk manager, reboot
Download and install safetynet-fix in the Magisk manager, reboot
Check with a safetynet checker app and you should pass
Do you like my work?
Than you can simply hit the thanks button and consider to spend me a coffee or a beer,
I'm doing this in my free time and it also costs a lot of money to buy hardware.
donate
Wanna improve your sound configs, control your charging current and more?
Now you can use my app to access all boeffla configurations, there will follow more functions.
Exynos4 Kernel Manager - Apps on Google Play
This app provides Boeffla sound control and other kernel + charging tweaks
play.google.com
Spoiler: How to install it?
Instructions
XDA:DevDB Information
[ROM][13.x][N7100][ALPHA] LineageOS 20.0, ROM for the Samsung Galaxy Note 2
Contributors
html6405
Source Code: https://github.com/html6405
ROM OS Version: 13.x T
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP 3.5.2
Based On: LineageOS
Selinux: permissive
Version Information
Status: Alpha
Created 2022-09-23
Last Updated 2023-03-10
*reserved
Thank you 6405.
Please keep up the good work.
Let me try it out will come up with reviews
Just downloaded the ROM.
The new themed icons seems to work for some apps.
The battery icon on the notification bar seems broken. You can't change the style or percentage.
Languages per app screen shows no apps.
I will share my real experience after testing some more.
It seems like you forgot to upload this ROM on Adroid-Filehost.
<accidentally double post removed>
Great job. Thanks for implementation. But I can't find the device/kernel/vendor sources in you github repros. Only device for LOS18.1
Update 29.09.2022:
Fixed GPS
Tried to fix surfaceflinger crash, let's test if it worked
It's Good
Unfortunately it isn't very good at all!
Not suitable as a daily driver yet!
Even the experimental LineageOS 19.1 GO builds here much more stable.
After some weeks of trying this ROM, I like to share my experience.
I started from a clean install / clean flash.
As usual, I really appreciate that you enhance the privacy and security with your degoogled Roms.
I know this is a based on a beta release of LineageOS and this ROM is in alpha release, but I like to help you improving this ROM.
Here is a list of things that are not working or are not working as intended:
Spoiler
- A lot of random reboots. Worst part, after the reboot ,WIFI won't work. You need to reboot the device manually again in order to fix this which is a huge waste of time.
The reboots mostly happens while browsing with the Brave browser or while typing long messages. I use OpenBoard as keyboard.
- A lot of (FC) force closes while opening some apps.
I can even barely use F-droid! Session and is even as good as unusable on this ROM!
Some apps like NewPipe are usable for a while, but suddenly closes for no particular reason.
Started from a clean slate, so all apps were clean installed as well.
- Very long startup times (Samsung Galaxy Note logo, not the LineageOs splashscreen)
- One day, I could no longer use my device.
When the device was booted, a message was displayed about factory reset and it will reboot automatically. After rebooting, the same message was shown again. The only option was to format the device using TWPR an flash everything over.
Fortunately, this happened only once, but that's a big problem that shouldn't happen again!
- After previous problem I decided to give encryption a try sine I got nothing to loose after all. Encryption still doesn't work!
- 5Ghz WIFI networks don't work. It's not a router problem because I can connect other devices just fine.
Problems occurs on our corporate network and my home network as well.
- Sometimes, the screen starts flickering black on pages with some more graphical intensive tasks, such as websites with embedded video's on it. I only could trigger this in the Brave browser and Firefox Focus.
- Colour correction mode won't work and isn't even available in settings. This prevent the blue light filter from working when it's late or dark. (orange tint).
- The battery icon is broken. You can't see the battery percentage.
Even if you enable circular and percentage in icon, the battery icon won't change.
- Display settings are not saved after a reboot. (example, go to settings>display and change the icon shape to squirqle and choose a custom font. After a reboot, the icon shapes will be circles again and custom font is default font.
Besides all the negative stuff, I also have some positive feedback as well.
I was really surprised (in a positive way) to see the Aurora Store was preinstalled.
This saves me some time downloading/installing it after a clean slate.
Receiving Android 13 on this device before same brand new Galaxy A devices was already a big surprise on its own.
Some nice to gets to make the ROM even more better:
Spoiler
- Make encryption work
- Completely degoogle LineageOS to protect our privacy even more. This will saves me some time after eery update of your ROM.
I referring to removing/replacing Google's DNS (default DNS is 8.8.8.8), Removing or replacing Google's SUPL (A-GPS).
Preferable better privacy respecting DNS:
Quad9: 9.9.9.9 149.112.112.112
Cloudflare: 1.1.1.1 1.0.0.1
Adguard DNS: 94.140.14.14 94.140.15.15
Here is a blog that can help you to understand the privacy problems and how to solve them:
https://www.reddit.com/r/degoogle/comments/cldohl
My goal is not to "tweak" or making any "cool mods " to your ROM.
My goal is to make it more privacy friendly by default for people who doesn't choose to flash MicroG or GAPPS.
- Remove the VIA browser or replace it with something more privacy respecting.
After a clean install, deleting it with ADB is often one of my first steps.
Bromite, Fennec or even Brave are some better alternatives.
- Optionally, you can replace the default AOSP system webviewer with Bromite as well.
- Optionally, a preinstalled F-Droid would be nice as well.
My apologies for the overload of information.
As usual, I like to help making this ROM as good as your previous ROMs or even better!
I hope my feedback is could be useful.
wiijordends said:
Unfortunately it isn't very good at all!
Not suitable as a daily driver yet!
Even the experimental LineageOS 19.1 GO builds here much more stable.
After some weeks of trying this ROM, I like to share my experience.
I started from a clean install / clean flash.
As usual, I really appreciate that you enhance the privacy and security with your degoogled Roms.
I know this is a based on a beta release of LineageOS and this ROM is in alpha release, but I like to help you improving this ROM.
Here is a list of things that are not working or are not working as intended:
Spoiler
- A lot of random reboots. Worst part, after the reboot ,WIFI won't work. You need to reboot the device manually again in order to fix this which is a huge waste of time.
The reboots mostly happens while browsing with the Brave browser or while typing long messages. I use OpenBoard as keyboard.
- A lot of (FC) force closes while opening some apps.
I can even barely use F-droid! Session and is even as good as unusable on this ROM!
Some apps like NewPipe are usable for a while, but suddenly closes for no particular reason.
Started from a clean slate, so all apps were clean installed as well.
- Very long startup times (Samsung Galaxy Note logo, not the LineageOs splashscreen)
- One day, I could no longer use my device.
When the device was booted, a message was displayed about factory reset and it will reboot automatically. After rebooting, the same message was shown again. The only option was to format the device using TWPR an flash everything over.
Fortunately, this happened only once, but that's a big problem that shouldn't happen again!
- After previous problem I decided to give encryption a try sine I got nothing to loose after all. Encryption still doesn't work!
- 5Ghz WIFI networks don't work. It's not a router problem because I can connect other devices just fine.
Problems occurs on our corporate network and my home network as well.
- Sometimes, the screen starts flickering black on pages with some more graphical intensive tasks, such as websites with embedded video's on it. I only could trigger this in the Brave browser and Firefox Focus.
- Colour correction mode won't work and isn't even available in settings. This prevent the blue light filter from working when it's late or dark. (orange tint).
- The battery icon is broken. You can't see the battery percentage.
Even if you enable circular and percentage in icon, the battery icon won't change.
- Display settings are not saved after a reboot. (example, go to settings>display and change the icon shape to squirqle and choose a custom font. After a reboot, the icon shapes will be circles again and custom font is default font.
Besides all the negative stuff, I also have some positive feedback as well.
I was really surprised (in a positive way) to see the Aurora Store was preinstalled.
This saves me some time downloading/installing it after a clean slate.
Receiving Android 13 on this device before same brand new Galaxy A devices was already a big surprise on its own.
Some nice to gets to make the ROM even more better:
Spoiler
- Make encryption work
- Completely degoogle LineageOS to protect our privacy even more. This will saves me some time after eery update of your ROM.
I referring to removing/replacing Google's DNS (default DNS is 8.8.8.8), Removing or replacing Google's SUPL (A-GPS).
Preferable better privacy respecting DNS:
Quad9: 9.9.9.9 149.112.112.112
Cloudflare: 1.1.1.1 1.0.0.1
Adguard DNS: 94.140.14.14 94.140.15.15
Here is a blog that can help you to understand the privacy problems and how to solve them:
https://www.reddit.com/r/degoogle/comments/cldohl
My goal is not to "tweak" or making any "cool mods " to your ROM.
My goal is to make it more privacy friendly by default for people who doesn't choose to flash MicroG or GAPPS.
- Remove the VIA browser or replace it with something more privacy respecting.
After a clean install, deleting it with ADB is often one of my first steps.
Bromite, Fennec or even Brave are some better alternatives.
- Optionally, you can replace the default AOSP system webviewer with Bromite as well.
- Optionally, a preinstalled F-Droid would be nice as well.
My apologies for the overload of information.
As usual, I like to help making this ROM as good as your previous ROMs or even better!
I hope my feedback is could be useful.
Click to expand...
Click to collapse
yes you're right. But fren: Android 13 on an ancient device (more than 10 years old). And at the end: it works!
Of course not very stable, maybe as you said android 12 (ever made by html64) is better, but also android 9 by comicox works fine.
In my case: i really can't use n2 as a primary or secondary smartphone. N7100 hasn't 4g, in my country is not more usable outside your home. So i want to se what is his limit. Even if there more crash and restart. no problem for me
There is a problem with the alarm clock. After opening the clock and then alarms that have been set in the clock app I only see a grey area for a set alarm. It is just a grey box without any text. Only after I click on the entry I see the details of the alarm.
PS: Any chance you could indicate in the file names what version(alpha, beta, final) it is from your point of view? May be an _alpha, _beta_, _final at the end of the archive file? Thx again for all the hard work!
Update 17.10.2022:
Fixed tethering
Synced with LineageOS sources
Fixed most missing / broken features
Fixed hang on boot screen
Updated gps.conf for A13
Update 18.10.2022:
Fixed crash when uninstalling any app
Hello my friend,
It looks like you've been working hard, I'm glad to hear you've made progress on Lineage20's development. I hope you can solve all the bugs so that we have a very stable version to use in our daily lives.
I'm looking forward to the release for the Note 10.1 tablets.
But I understand that there is still a lot of work ahead.
But here's my respect for your work.
lineageos 20 on my device crashes when i unplug the charger it turns off when i plug it back in it comes back on
Tranvy2022 said:
lineageos 20 on my device crashes when i unplug the charger it turns off when i plug it back in it comes back on
Click to expand...
Click to collapse
Hmm strange, just tried it again on my device, it behaves correct, stops charging and wakes up, are you using a n7100 or a different model number?
I really don't see any problem here.
Hi
I try to pit a custom rom tó my gt n7100 16 gb.
The rom is ok, its work fine, bút i cant install google apps őackage, always runt to error 70 in trwp, not enough disk space. The phone has got 8-10 gb free space . What is the problem?
html6405 said:
Code:
/*
* 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.
*
*/
Hi,
here you can find my version of LineageOS 20.0 for our Samsung Galaxy Note 2 (3G).
At first I want to thank @rINanDO, @ChronoMonochrome for all your work on these devices!
This is an alpha version, it's not finished from the LineageOS side and also not from mine.
Most of the LineageOS specific features are missing or not working yet,
please do not report bugs.
Attention:
As it looks like does the device stuck at the "Samsung Note II" screen when you boot out of TWRP,
simply touch the screen with your fingers and it will move on...
I try to find out whats going on there
If you wan't to enable the back gesture for gesture navigation, do the following:
adb shell
setprop toggle_navbar true
You can do the same to disable it.
Here you can see how far everything is working for now.
Spoiler: Whats working
Boot
Audio
Bluetooth
Graphics
Cameras
Sensors
Wifi
GPS
USB
Video playback (HW/SW)
Tethering via USB
RIL
OTA-Updates
Tethering via WIFI and Bluetooth
much more...
Spoiler: Whats not working
NFC
Encryption
BT audio in a phone call
Network monitoring because of missing eBPF
Maybe random reboots
Spoiler: Links
TWRP
ROM Android-Filehost
ROM Mega
Spoiler: Changelog
29.09.2022
17.10.2022
Spoiler: How to improve GPS
You could use a gps.conf from https://app.box.com/s/w57s1v1n3hie7l5lk28i for your location and replace /vendor/etc/gps.conf.
Or you try GPS Server Optimizer app for a faster 3D fix.
For both methods you need root rights.
I would recommend to use microG instead of BitGapps,
here you can find the installation instructions:
Spoiler: microG instructions
Download Magisk 24.1 and flash it via TWRP (yes, flash the APK file), reboot
Open Magisk and update the App (and do a reboot if it's asking)
Enable Zygisk in Magisk
Download and install microG installer in the Magisk manager, reboot
Download and install safetynet-fix in the Magisk manager, reboot
Check with a safetynet checker app and you should pass
Do you like my work?
Than you can simply hit the thanks button and consider to spend me a coffee or a beer,
I'm doing this in my free time and it also costs a lot of money to buy hardware.
donate
Wanna improve your sound configs, control your charging current and more?
Now you can use my app to access all boeffla configurations, there will follow more functions.
Exynos4 Kernel Manager - Apps on Google Play
This app provides Boeffla sound control and other kernel + charging tweaks
play.google.com
Spoiler: How to install it?
Instructions
XDA:DevDB Information
[ROM][13.x][N7100][ALPHA] LineageOS 20.0, ROM for the Samsung Galaxy Note 2
Contributors
html6405
Source Code: https://github.com/html6405
ROM OS Version: 13.x T
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP 3.5.2
Based On: LineageOS
Selinux: permissive
Version Information
Status: Alpha
Created 2022-09-23
Last Updated 2022-10-17
Click to expand...
Click to collapse
Say what ? Did I miss this ? Big Up HTML !!!!!
stefannn said:
What is the problem?
Click to expand...
Click to collapse
The problem ist the free space of the system partition,
I've never tested gapps on this ROM and will not recommend them.
But if you wan't to install them you maybe have to expand the system partition before (with parted).
Or try to find a smaller package.
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.
*/
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 13.x (T),which is designed to increase performance and reliability over stock Android for your device.All the source code for LineageOS is available in the LineageOS GitHub repo.And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.Official LineageOS website : http://lineageos.org
About Optimizations
Android Runtime
Disable debugging related features
Compile with D8 optimizations
Adjust watchdog timeout
Android Bionic
Sort host cache in-memory for performance
Switch to jemalloc memory allocator
msmset and pthread related changes
Android Build
Compile with ARMv8-2a-dotprod optimizations
Compile with O3
Compile with lse+fp16
Don't compress resources and assets
Use dexpropt speed
Increase heap size and use aapt2
... and sqlite, zlib related optimizations
Android Recovery
Allow installation of unverified zips i.e the most functional change ever
Android FWB
Reduce blur intensity to ease CPU/GPU
3 finger screenshot support (Please check under Gestures)
Added related missing permissions
SurfaceFlinger related optimizations
View/Layout optimizations
Android Telephony
Latest prebuilt APN from Stock
Updated CarrierConfigs from CAF
Additional cherry-picked IMS related fixes
Android System
Safetynet fixes
Improved Magisk evasion fixes
Disabling data for all connection interfaces and not just mobile data
Additional alarms and ringtones
Dialer
Allow auto-call recording as per country laws
UI changes
DocumentsUI
Start with Internal Storage instead of Downloads
Gallery2
Start with albums activity
Trebuchet
Allow double tap to sleep on homescreen
Updater
Allow local update feature
About Issues
MotoCamera's night mode doesn't work correctly (same as LineageOS), replaced by Aperture, use GCam if needed. MotCamera4 fixed thanks to Marc
NR only mode (5G only mode) works with Jio only. For using 5G on other ISP, use NR/LTE or any other bands, during heavy network traffic, it switches to 5G and fallbacks to 4G during power save automatically
Downloads Links
LineageOS 20.x (Unlocked Bootloader) :Link : https://drive.google.com/drive/folders/1wXGs7pitUvOCETdCHjVsvpVD3iilbiNl?usp=share_linkGoogle Applications :Not required (has inbuilt minimal set of Google Applications including SetupWizard)Flashing and updatingLineageOS clean install :- (Optional) Flash the boot.img recovery from the ROM zip with Fastboot- (Optional) Wipe the data & cache (Backup to make sure not to loose data)- Flash the LineageOS ROM zip from the Recovery- Reboot to recovery again- (Optional) Every additional zip you want to flash like Magisk- Reboot to systemLineageOS Update using "Local Update" feature :- You need to be on an existing ROM developed by me- Download the ZIP from download link above and storage in local storage (example Downloads folder)- Go to Settings -> System -> Updater- Click 3-dot buttons and select Local update- Select the zip using File Manager- Let it update (takes some time)- RebootIssues and reports- Report issues only if you are using the ROM kernel- If an additional mod is installed, make sure it's unrelated, and mention it- Make sure the issue wasn't discussed earlier in the threads- Share a log of the error with CatLog for example- Make sure you also tell the ROM version you're using
XDA:DevDB Information
[ROM][13.0][OPTIMIZED] LineageOS 20 for Moto Edge 30
Contributors
Daedroza, Albert
Source Code: https://github.com/daedroza
ROM OS Version: 13.x Android T
ROM Kernel: Linux 5.4.x
Version Information
Status: Stable
Created 2023-01-26
Last Updated 2023-01-26
Changelog (You can use updater to update from local storage)
Android 13 Blobs + Android 13
June 25, 2023
Sync with June security patches
Added MotCamera4
Added Android 13 blobs
Updated system wide ad block hosts
Android 12 Blobs + Android 13
May 15, 2023
Sync with May security patches
Added Dolby support
Minimal ad block (system-wide, all apps)
April 18, 2023
Sync with April security pathces
Even more aggressive battery optimizations
Wifi optimizations (2.4GHz bonding)
More fluidity at 60HZ
March 27, 2023
Hot-fix for 5G Networks
Enabled 5G by default if supported
Enabled 5G Voice over Network (VoNR)
March 25, 2023
Sync with March security patches
Aggressive inline optimization using LTO
Aggressive sleep optimizations
Respect restricted apps
Platform fixes for GMS package
Fixed a bug where Android Studio's debugger didn't connect (for developers)
February 19, 2023
Complete fix for SafetyNet
February 13, 2023
Synced with February security patches
More SQLite optimizations and updates
Reverted to Lineage's UDFPS implementation
Use Aperture instead of MotCamera4 (crashes with face beauty and night mode...)
Appreciate your kind efforts. Feels perfectly smooth and stable.
Just a noob question regarding the "Safetynet fixes", my device still cannot pass the CTS (which I assumed would be one of the fixes compared to stock LOS 20). Or may be I misunderstood the whole thing. Thanks.
rjawan said:
Appreciate your kind efforts. Feels perfectly smooth and stable.
Just a noob question regarding the "Safetynet fixes", my device still cannot pass the CTS (which I assumed would be one of the fixes compared to stock LOS 20). Or may be I misunderstood the whole thing. Thanks.
Click to expand...
Click to collapse
Thanks for your response!
I've picked "most" of the patches across different ROMs but there might be one or two missing. For time being, you can use Magisk and Zygisk to hide your relevant apps.
For me, using Magisk + Zygisk Hide on Google Play Store gave certified status which is good enough for me. At the moment, I am using ProtonAOSP's related patches (mostly with exception for others) for SafetyNet from Android 12 but it seems Android 13 is bit different. I will take a look into it however I am sure you can get it done easily using Magisk + Zygisk combo for time being.
EDIT: Magisk fixed. Please use builds after 18th February!
is any of these improvements suppose to improve longevity of battery? (except lowering blur, that i can understand ) wondering if this build is for me over default LOS.
possible to see build without google stuff included?
alekksander said:
is any of these improvements suppose to improve longevity of battery? (except lowering blur, that i can understand ) wondering if this build is for me over default LOS.
possible to see build without google stuff inincluded
Click to expand...
Click to collapse
From a non developer's perspective, ROM is quite smooth. Most layers of the code are optimised. There are some functional changes like able to install unsigned packages in recovery which official Lineage doesn't allow.
For battery life, I get maximum 10 hours of screen on time. I never crossed that mark. Usage is no social media and mostly video browsing (means no screen touches with 480p/720p streaming) @ 60HZ/48HZ combo.
Regarding Google Play services, it was a design decision. I like functional changes and hence kept a minimal package that is oriented towards battery life. I had done my fair share of living without Google services and I think modern devices are fairly powerful now.
I had done a comparison with Lineage's recommended MindTheGapps package and I get additional 2 hours of screen on time (maximum 10 hours of screen on time as said before).
profound answer. thank You.
Daedroza said:
I had done my fair share of living without Google services and I think modern devices are fairly powerful now.
Click to expand...
Click to collapse
does it mean no plans to release g'less variant?
Daedroza said:
From a non developer's perspective, ROM is quite smooth. Most layers of the code are optimised. There are some functional changes like able to install unsigned packages in recovery which official Lineage doesn't allow.
For battery life, I get maximum 10 hours of screen on time. I never crossed that mark. Usage is no social media and mostly video browsing (means no screen touches with 480p/720p streaming) @ 60HZ/48HZ combo.
Regarding Google Play services, it was a design decision. I like functional changes and hence kept a minimal package that is oriented towards battery life. I had done my fair share of living without Google services and I think modern devices are fairly powerful now.
I had done a comparison with Lineage's recommended MindTheGapps package and I get additional 2 hours of screen on time (maximum 10 hours of screen on time as said before).
Click to expand...
Click to collapse
10 hours is impressive, even with just 60hz. So that means if you do not have the MindTheGapps you have 2 hours extra battery? Or is it 2 more hours if you have the MindTheGapps vs the Google bloat?
Thanks
alekksander said:
profound answer. thank You.
does it mean no plans to release g'less variant?
Click to expand...
Click to collapse
No plans as such. Building Android 13 is already very costly for me with these optimizations. Building it twice once with and without is something I am not looking forward to simply because of my constrained resources. I do a lot of building outside Lineage too, so simply cannot waste my SSD read/write cycles. Secondly, I already shipped first version with those services built-in. Removing those in next update will cause a lot of problems and could be fixed with clean flash only.
JorgeTone said:
10 hours is impressive, even with just 60hz. So that means if you do not have the MindTheGapps you have 2 hours extra battery? Or is it 2 more hours if you have the MindTheGapps vs the Google bloat?
Thanks
Click to expand...
Click to collapse
MindTheGapps is a more complete Google services package which includes accessibility and few other components. My minimal built-in package doesn't include those. If you require accessibility services, my recommendation is to use official Lineage with MindTheGapps.
Got it.
Really last question – does this ROM works anything different to LOS regarding UDFPS? (It doesn't seem so, but i prefer to ask since i cannot decode most of the changelog acronyms).
alekksander said:
Got it.
Really last question – does this ROM works anything different to LOS regarding UDFPS? (It doesn't seem so, but i prefer to ask since i cannot decode most of the changelog acronyms).
Click to expand...
Click to collapse
The UDFPS implementation is same as official build, no difference whatsoever except that my build has slightly more screen flashes because the UDFPS implementation doesn't support multi rect correctly. A workaround is present in official build that causes more battery life to be consumed.
For now that workaround is reverted in my build because I'm trying to understand how far it's effect is on battery life.
I don't think you will even notice it if you use 90HZ+ or more as default.
EDIT: Reverted to original Lineage implementation on new release!
rjawan said:
Appreciate your kind efforts. Feels perfectly smooth and stable.
Just a noob question regarding the "Safetynet fixes", my device still cannot pass the CTS (which I assumed would be one of the fixes compared to stock LOS 20). Or may be I misunderstood the whole thing. Thanks.
Click to expand...
Click to collapse
Hi @rjawan , please use build from February 19, 2023. It has complete SafetyNet fixes. Remember to remove Magisk as some apps still detect it and banks might app not work because of it. But CTS profile does pass and my bank app works now. Enjoy
Daedroza said:
Hi @rjawan , please use build from February 19, 2023. It has complete SafetyNet fixes. Remember to remove Magisk as some apps still detect it and banks might app not work because of it. But CTS profile does pass and my bank app works now. Enjoy
Click to expand...
Click to collapse
Thank you. Amazing work. Works like a charm, just as you said. Passed the CTS test straight away. BTW I am not using Magisk to begin with so have nothing to do on that front. Cheers mate. Thanks.
Daedroza said:
Changelog (You can use updater to update from local storage)
March 25, 2023
Sync with March security patches
Aggressive inline optimization using LTO
Aggressive sleep optimizations
Respect restricted apps
Platform fixes for GMS package
Fixed a bug where Android Studio's debugger didn't connect (for developers)
February 19, 2023
Complete fix for SafetyNet
February 13, 2023
Synced with February security patches
More SQLite optimizations and updates
Reverted to Lineage's UDFPS implementation
Use Aperture instead of MotCamera4 (crashes with face beauty and night mode...)
Click to expand...
Click to collapse
Hi, thanks for this build.
March 27 changelog ?
Thank you for making this great version of lineage, it really is very polished and it runs 11/10, the battery lasts a long time and the fluidity is magnificent, it passes the safetynet verification by itself, which is greatly appreciated, I loved it a lot, I wish it could be added the "amoled" night mode (I don't know if it already has it and it's hidden) and the game space and without a doubt I would stay in this rom forever
Roonicks said:
Thank you for making this great version of lineage, it really is very polished and it runs 11/10, the battery lasts a long time and the fluidity is magnificent, it passes the safetynet verification by itself, which is greatly appreciated, I loved it a lot, I wish it could be added the "amoled" night mode (I don't know if it already has it and it's hidden) and the game space and without a doubt I would stay in this rom forever
Click to expand...
Click to collapse
Check in display dark theme and there is a menu there
Rom is very stable and smooth but there is a very huge battery drain in idle mode around 2-3%/hr even after fresh install and can you please add network speed indicator on status bar on your next update if possible thanks in advance
aslam2121 said:
Rom is very stable and smooth but there is a very huge battery drain in idle mode around 2-3%/hr even after fresh install and can you please add network speed indicator on status bar on your next update if possible thanks in advance
Click to expand...
Click to collapse
You can use Battery Manager to detect applications that are sucking battery life or just check Battery Usage graph. Usually few applications hold some wakelock to perform activities in the background which usually ends up being the culprit. My recommendation is to disable applications running in background and disable background mobile data usage.
If you have done clean install, I recommend waiting for cache to build which generally takes time if you have lots of applications.
@aslam2121 : Check with new April build, there are more battery optimizations which reduces random wakelocks.
Thanks for this awesome ROM, any chance to add Dolby Atmos? (Without rooting the phone)
Where to get the boot image? And can I flash magisk zip directly from recovery?