Related
Introduction & Disclaimer:
If you've ever flashed a new rom, updated a firmware, or plain reformatted - all because you just had to have the newest __blank__? Then you have come to the right place.
Nightlies are addictive and exciting, but can be unpredictable and sometime unstable. We take no resposibility for what you do or what happens when you do it.
READ THE FAQ's!
xda member Docent has kindly prepared an easy to follow faq tailored to the AmeriCanAndroid userbase.
You can find (and please DO find) his FAQ here
Older FAQ's by copenhagen: here, here, and here.
(Most of the tips are still pertinent to this build)
fyi:
Cope's SD Thread: http://forum.xda-developers.com/showthread.php?t=898831
WarrenBread Thread: http://forum.xda-developers.com/showthread.php?t=927671
Click to expand...
Click to collapse
Click to expand...
Click to collapse
{
"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"
}
Image Gallery:
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Description:
Cyanogen CM7 (Gingerbread 2.3.7) 100% HTC-LEO cm base
latest updates always compiled from git source.
changelog: CM7 Changelog WIKI
Warrenb213's AmeriCanAndroid Kernel r823
Includes optional rootfs.img that allows to boot build from magldr (!readme! in /sdcard/Android/SDMAGLDR)
Ad-blocking hosts file (inc. audiogalaxy friendly)
PPP data implemtation
Optional automatic data/app backup and restore (bkup2sdext)
you do NOT have to partition your sdcard to run this build. All you need is a single fat32 partition, however extended features are available to those who sport a partitioned sd card
Check post 3 for user modifications such as sense theme and round battery icons.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Changelog:
Current Release:
03.08.12 - Update
-cm code updates from jan 19 to march 08
??-hd recording still flakey, use high??
-included a themed htc_ime generated from the online generator install apk from /sdcard/android/androidapps or /sdcard/backup/app. (activate through settings->keyboard after installed) ***the htc_ime keyboard is amazing btw the features are incredable test it even for a minute and youll understand***
Credit goes to gimpsta for this lovely keyboard. >> http://www.gimpsta.com/themer/
-*GSensor-Calibration tool: To use it
In terminal emulator type, su (return)
bma150_usr( lay phone flat on back and hit return )
exit(return), exit(return and close).
===ALL users read below===
its important that you read the section in
the installation and updating section before updating.
Click to expand...
Click to collapse
Previous Releases:
01.19.12 - Update
-cm code updates from jan 11 to jan 19
-new boot animation from evo1rs! so good.
-updated the builds implimentation of sqlite which should give it a bit better performance
01.11.12 - Update
-cm code updates from jan 02 to jan 11
01.03.12 - Update
-cm code updates from dec 20 to jan 03
Click to expand...
Click to collapse
Installation & Updating:
Installation Video-Tutorial for aca users by noobielameoInstallation & Updating Proceedure is the same!:
Download the build to your pc.
1. americanandroid.7z -> unzip!
2. copy folder unzipped\AmeriCanAndroid\Android -> to -> \sdcard\Android
(COPY THE WHOLE FOLDER.. NOT JUST INDIVIDUAL FILES!!!!!!)
(!If you are UPDATING.. choose overwrite when prompted - no need to delete anything!)
3. in winmo, run clrcad.exe and haret.exe in the \storage card\Android\ folder. OR
(alternatively install exceller bootloader for winmo for one click or AUTO launch of Android OS)
first boot always takes a long time be patient, it will work, and future boots do not take as long.
bkup2sdext users read below
- To enable backup of apps and data to your sd-ext partition edit /system/build.prop change
@ the bottom aca.bkup2sdext.enable to =1 (change back to 0 to disable)
*to enable restore of /data/data edit /system/etc/shutdown.d/02shutdown and add data after
for i in app app-private so you end up with
for i in app app-private data;
save, then reboot.
-!! During day to day use; it is MOST important to SHUTDOWN and not pull batt,
as this is when your data gets backed up to the sd-ext partition.. !!
- Your device will auto restart after about 5 to 10 minutes from when android starts loading.
This shut down is required to complete the restore of existing data to a new build.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Downloads:
03.08.12 - UPDATE
AmeriCanAndroid SD - http://www.mediafire.com/?q55i1z518ddra6r
mirror - http://uploadmirrors.com/download/12F09AQL/32-AmeriCanAndroid_030812_sd_.7z
discussion for this release starts on this page.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Donations:
if you truly feel we are deserving, your donations are appreciated <--clicky!.
Coffee to keep us awake and working
THANKYOU to those who have already done so. We'll keep working on making you a better build as best we can.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Major thanks to:
google - obviously...
cyanogenmod team - for the great effort they put into their very high quality work. the ground floor to the roof and then some. Amazing Amazing.
copenhagen - I saw we needed to thank you too Mr Canadian. haha. You rock.
warrenb213 - its great working with you... its way better to have an team mate for these projects. and you've brought alot to this build. thankyou so much
mdj - researching your builds have helped us tremendously in accomplishing this.. major thankyou.
lithid - your guidance and straight forward tips have been most beneficial
shub - for the great builds till u nixed them.
mattfmartin, noellen, docent - xda bruthers from another mother.
michyprima - you started copes love for nightlies.. its your fault! and he thanks you.
diem - for the gps fix
linus torvald - for starting something so amazing!
tytung - for sharing your great work on the hd2's gps implementation
ianscott888 - for the fantastic blender tutorials and 3d android rig set for our animation!
pwhitrow(bootlogo), evo1rs(bootanimation), uzi2(support), docent14(support), playstation(support), krisdelisle(support), and the many other (sorry if i forgot u) users who have helped maintain the sanity.
xda - for the forums.. the info.. and the users
to everyone else we missed. Thankyou
working for a community on a community project; to those who came before us, thankyou for everything you have done.. Thankyou.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Source:
The AmeriCanAndroid build and Warren's kernel are online @ gitorious:
https://github.com/AmeriCanAndroid/
https://gitorious.org/aca-kernel
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Cleaned at request of the good Canadian.
changelog archive
User Modifications: (under dev)
100 point Circle Battery Notification Bar
modded by cmillens
http://forum.xda-developers.com/showpost.php?p=12189777&postcount=2883
HTC Sense Theme For AmeriCanAndroid
modded by Anthonayy
http://forum.xda-developers.com/showpost.php?p=12018240&postcount=2167
T-Mo USA Netflix App
maintained by Sprintusa
http://forum.xda-developers.com/showpost.php?p=14597920&postcount=10251
Click to expand...
Click to collapse
maintained user modifications are listed here
(pm us if you have something worth posting)
Click to expand...
Click to collapse
Changelog Archive:
Code:
[color=grey]Previous Releases:
12.20.11 - Update
-cm code updates from dec 7 to dec 20
12.07.11 - Update
-cm revision updates from nov 29 to dec 7
-evo1rs caught a small init.d error - have corrected
11.29.11 - Update
-cm revision updates from nov 27 to nov 29
11.27.11 - Update
-cm revision update to 7.2
-cm updates from nov 7 to nov 25th
11.07.11 - Update
-new super user app 3.0.6 and su binary 3.0.3
-new market 3.3.11
-added "fixed" vold until we can find the proper source code -thx evos!
-updated boot animation from evo1rs
-cm revision update to 7.1
-cyanogenmod updates from oct22 to nov6th
10.22.11 - Update
-cm updates from oct 17 to oct 22
-Evo1rs fixed the pixels in the boot animation thx buddy :)
-changed the lcd density to 160 to avoid the market "this device is not compatible" error message. YOU MAY HAVE TO clear data & defaults in settings appli market+reboot.
-35 kernel NOT ready to boot sd yet but its being looked into.
10.16.11 - UPDATE:
-new revision of gingerbread 2.3.7 :)
-cyanogenmod changes from 0828 to 1016!
-welcome back! :) man that felt like forever.
[B]-New Revision of Android 2.3.7 MAY require a fresh install, so backup your data. New market may require a fix permissions / and or clear data in settings->applications.
-Starting with 080111 and later, users can edit /sdcard/android/startup.txt [I]prior to booting [/I]to adjust LCD_DENSITY, GPS_ZONE, and DATA_SIZE (data.img)
(ie: the default lcd_density of ACA is 167. Edit the lcd_density= value to 240 to get standard sized icons and fonts)[/B]
08.28.11 - UPDATE:
ACA Build updates:
-Added Tytungs GPS 2.1
===
Kernel Updates: r823
-Implemented RNDIS again(tried long ago), just Tytung's working
version. Kudos to tytung for the candy settings.
-Set config_hz back to 1000.
-Sourced from jdivic and mdebeljuh: Wakeup Lag Fix for AUO panels
===
Cyanogenmod Updates: (some may not apply to us - Updates from 081711 to 082811)
-SystemUI: Add 4g iconography
-telephony: add support for HSPA+
-Merge "telephony: add support for LTE and EHRPD" into gingerbread
-add missing prototype from OMAP4 FM header merge
-telephony: add support for LTE and EHRPD
-Merge "Log Wifi NativeCommand exceptions" into gingerbread
-Merge "Fix: Do not change music volume if screen off and no music playin...
-Merge "Fix exception in legacy USB support" into gingerbread
-Merge "SystemUI: Show mic-less headphone icon in status bar (1/2)" into ...
-Merge "Notification PowerWidget: Additional SoundMode: Vibrate/Silent" i...
-Merge "Revert "Change Finnish time format to use ':' instead of '.'"" in...
-Merge "frameworks/base: bluetooth: AVRCP 1.3 feature changes" into ginge...
-Fix: Do not change music volume if screen off and no music playing Comment
-Log Wifi NativeCommand exceptions
-Fix exception in legacy USB support
-SystemUI: Show mic-less headphone icon in status bar (1/2)
-Notification PowerWidget: Additional SoundMode: Vibrate/Silent
08.17.11 - UPDATE
ACAKernel r816 updates:
- kgsl updates:
*msm_kgsl: Move kgsl_sharedmem_init to module load
*kgsl_sharedmem_init/kgsl_sharedmem_close only need to be called once,
so move them to the the module load and close functions so they can be
available through the life of the module.
*msm_kgsl: Optimize TLB flushing
Only flush TLB when it is absolutely nessasary as opposed to
flushing it on every map and unmap
*msm: kgsl: Fix a potential subtraction overflow issue
*msm_kgsl: Reuse vmalloced memory buffers
Memory buffers that are vmalloced and can be freed are put
into a free list and reused later if an allocation of same size
is required.
- Tweaked the Audio levels a bit more.
- Added the HTC Auto White Balance Calibration to the leo.
- Modded compile script a tid bit
ACABuild Updates 081711:
- various aca build tweaks
- cyanogenmod updates from 0812 to 0817
08.12.11 - UPDATE
adjusted lcd auto backlight levels
adjusted light sensor lux levels
adjusted some notification led settings in the build
enabled mms content disposition support (lets see if this fixes our mms issues)
added some changes from [url]https://github.com/CyanogenMod/android_device_htc_leo/commit/2629ed278367ef1ce4993a329546e0b47757adfc#diff-11[/url]
cyanogenmod changes from Aug 7 to Aug 12
080711 - UPDATE
-massive cyanogen mod updates from aug 01 to aug 07
-updated gpslib to 2.0 (thx tytung)
080111 - UPDATE
-ability to edit the startup.txt in /sdcard/android/startup.txt prior to booting to adjust: (thx shosts and satan!)
lcd density (ie 167 to 240)
gps region (ie us to eu or ca)
data size (in MB)
-cyanogenmod source updates from 0729 to 0801
-gps cleanup fix applied in the build
-removed the davik2sdext was causing boot issues.
072911 - UPDATE
-new version number GRJ90 and Gingerbread 2.3.5
-cyanogenmod updates from Jul 22 to July 29
-you may need a new data img. (but as usual try ur existing first.. make a backup before you try)
-found and fixed an issue that caused "can only boot once" issue for some sd users
-updated to tytungs gps libs 1.9
-fixed VPN (tun module wasn't loading)
-added Jag's Fancy Schmancy Compass (Thanks Jag!)
bk2ext:
-disabled bk2sdext by default. it can be enabled in build.prop
-device only shuts down on first boot/upgrade if u have bk2sdext enabled
-added some checks against double mounting sdcard to sd-ext (no longer will happen)
-re-enabled backup of /data/-->data<-- in bk2sdext routine, but left restore out. (its good to have a backup of your data just in case)*
-still looking for the lib audio fix that is fixing this crash with skype.. (looking for the source code to fix it not a .so file)
^^however.. its probably something cyanogen will fix before i find it.
072211 - UPDATE
-new kernel from warrenb. ACAKernel r0719
-cyanogenmod updates from july 15 to july 22
-completely rebuilt from scratch. build now has permissions / ownership on OS files- set as per cm's specifications.
071511 - Update
-new kernel from warrenb. ACAKernel r0714
-added gsensor calibration tool[B]*[/B] - thankyou for the tip evo1rs :)
-updated gps libraries[B]**[/B]. thanks tytung and dan1j3l ([url]http://forum.xda-developers.com/showthread.php?t=1100114[/url])
-cyanogenmod updates from july 11 to july 15
070911 - Update
-rootfs now 7mb
-updated boot logo :) thanks to xda user pwhitrow
-swapped in a different default acdb file for louder sound
-cyanogenmod updates from july 05 to july 09
070511 - Update
-kernel now brought back up to date. with additional updates
-smaller rootfs
-cyanogen mod updates fomr june 23 to july 05
062311 - Update
-updates from june 10 to june 23 (lots of updates from them) lol may
-work done on kernel to bring it back. It is going to get updated again,
but its going to take time and lots of testing. however. I must say. YAY.
so. back to 0512andAbit.
-update like normal. no extra stuff needs to be done.
061011b - Update
===b release
-past 12 hours or cyanogenmod code updates
-updated kernel from warren addressing a few issues
-using a different ip-up-vpn file now in the compile... hopefully resolves vpn issues.
===inital release
-vpn more work done on vpn
-usb mass storage more work done here
-we added "push back button to ignore incomming call"
-did some more tweaking to the boot animation to bring it down in size a little
-incorporated past 12 hours of cyanogenmod code updates
-work on our implementation of the notification led code
-new kernel r610 from warrenb213
060911 - Update
-cyanogenmod code updates from June 8 to June 9 2011
-attempts to resolve vpn implementation issues
060811 - Update
-cyanogenmod code updates from June 7 to June 8 2011
-new kernel from warren r608*
*removed 2 git patches which were causing potential stability issues
*interactive gov: lowered sample rate from 80000 to 40000
*added TinyRCU
*added jhash3
*reintroduced 128mhz option(currently set as default lowest in build)
*updated ppp driver
060711 - Update
-cyanogenmod changes from June 5 to June 7
-new kernel from warrenb r0607
-fixed twitch in the boot animation during the dance (thx evo's)
-thread has now passed 1000 pages. and over 1 million views. ;)
060511 - Update
-cyanogenmod changes from may26 to June 5
-optimized the build for size in mb (total dl size) (system.ext2 is smaller now down to 192mb from 224mb)
-optimized boot animation .. less loops on flag part
-build is speedier then last two releases
052611 - Update
-cyanogenmod changes from may 21 to may26
-new kernel 526 warrenb213
-new bootanimation by evo1rs
-thx to ACAdevteam the rotary lock is now working (and fix currently pending approval for push into cm7 code for all smartphone devices with similar symptoms.
052111 - Update
-cyanogen mod updates from may 19 to may 21
check our git for changes (link @ bottom of post)
-updated kernel from warrenb213! solves previous timeout issue "F.C/Wait" Screen / among other changes.
check out warren's kernel git for changes (link @ bottom of post)
051911 - Update
-cyanogen mod updates from may 16 to may 19
-check the first post for link to ACA's git for more info
Kernel Updates ACA kernel 518c:
-[B][U]major major improvements to bt.[/U][/B]
-check first post for link to warrens kernel git for more info
051711 - UPDATE
-cyanogenmod changes from may 12 to 16
-new custom high-res fullscreen boot animation (its not finished yet / evo1rs & I are working on this atm)
-highest quadrant score we've ever achieved.
-enabled low power mode for bt radio/drivers
-removed unused shutdown options ie: recovery and bootloader
-including netflix app
-mms receive changes.. hopefully this cures our inability to download mms messages once and for all
-tweaked mediaprofiles.xml by evo1rs! Thx brother :) nice work.
Kernel Updates ACA kernel 516:
-tun support now built into kernel (no module file needed)
-improved task schedualing and io handling
-improved memory optimization
-ethernet updates
-overclock the camera
-sensors, cpu governer, usb updates
051211 - UPDATE
-fixed usb to pc functions.
-cyanogen mod updates from may 10 to may 12
-new 3d rendered boot animation from evo1rs (amazing i have to say.. your in for a treat)
Kernel Updates ACA kernel 512:
-stop WiFi from dieing. Originally from CM kernel.
-ext2: Fix link count corruption under heavy link+rename load
-vfs_rename_other() does not lock renamed inode with i_mutex. Thus changing
i_nlink in a non-atomic manner (which happens in ext2_rename()) can corrupt
it as reported and analyzed by Josh.
-msm: i2c: Hold mutex around i2c_xfer and during suspend/resume.
-ip6ip6: autoload ip6 tunnel
-Add necessary alias to autoload ip6ip6 tunnel module.
-USB: f_mass_storage: Disable write cache support
-Add USB_ANDROID_RNDIS_WCEIS option.
-ARM: 6490/1: MM: bugfix: initialize spinlock for init_mm.context
-ARM: Stop irqsoff trace on return to user
-cpufreq: Prevent memory leak in cpufreq_stats on hotplug
05/10/11 - UPDATE (* = changes since last [B]official[/B] release)
-cyanogenmod changes for past 12 hours
05/09/11* (050811c - this was a typo on my part sorry)
-warren has done up a new kernel with bt specific changes. ACA Kernel 508 - by warrenb213
-also did work on PPP data reordering.... check his kernel git for more details (link in first post)
-lots of overlay changes in the git.. again link in first post to our git for more details.
-removed lithid's gapps.. to many issues.
-cyanogen changes from the past 12 hours.
-included latest titanium backup again /sdcard/android/androidapps/ (this will auto install on first boot and be subsequently moved to /sdcard/backup/app/HERE on first shutdown.
05/08/11b*
-cyanogen updates since last compile
aca changes:
-changed max connection in audio.conf back to 1 to test
-the ACA default cricket notification sound is back. found a duplicate entry in build.prop
-updated gapps with lithids precompiled packages dated 05/04/11 donno what his date convention is either way its newer then ours.
lithid builds for supersonic device. [url]http://forum.xda-developers.com/show....php?t=1056101[/url]
(has the exact same googletalk2 we've included for the past week
other gapps have been updated including vending)
05/08/11*
cyanogen updates from may 7 to may 8 inc:
hci (bt components)
settings app
voip
05/07/11*
cyanogen updates from may 6 to may 7 inc:
superuser
settings
music
mms
filemanager
dspmanager
contacts
cmparts
camera
aca changes:
-changed to master=true
in system/etc/bluetooth/audio.conf
05/06/11 - UPDATE
-additional data stability changes (see ACA git for details)
-cm updates to may 6
-updated some components in the rootfs
-another improvement on speed and response with this build.
-AVRCP IS NOW WORKING!
05/05/11 - UPDATE
-GB revision update from GB H40 to GB I22
-cyanogen changes from may 1 to may 5
-new kernel: includes unique bt mac addressing 504
05/01/11 - UPDATE
-GB build revision update to 2.3.4
-Cyanogenmod revision update to 7.1
-includes cedesmiths v8b5 ril_wrapper
-fix for gps by diem & gaunner still being used
-cyanogen mod changes from April 27 to May 1
-added tcpthrough put tweak to rootfs
-added show real number for VM retrieval to build.prop
-nowgoogle talk voice & video chat capable
[B]AmCanAndroid Kernel v501 - Presented by Warrenb213:[/B]
[I]enabled oc'ing[/I] - (use oc'ing at your own risk)
[I]older history moved to post #3[/I]
04/27/11 - UPDATE
-default lcd density for ACA is now 167 (didnt forget this time)
-gps fixed (sorry about last build... transition period.. ironed out)
-cyanogenmod updates from april 25 to 27
-updated rootfs
-tweaked hd recording/playback settings for your testing
-hidden wifi & adhoc networking is comfirmed now working
(thanks to our updates over the weekend and warrens brilliance!) * sparkle sparkle *
-made major changes to the gps.conf file to allow for faster gps lock times [B](fasterfix / any gps fast fix software is now NOT RECOMMENDED) the only gps changes you should be making is the old style where you edit gps.conf and change the "us" entries to your own.. ie "gb" "pl" "ca" etc.[/B]
04/25/11 - UPDATE
-default lcd density for ACA is now 167 (dont say anything until you see it)
-missing pixels are NOW gone (filled in rather) in the notification bar (haha i double checked this time.... im NOT mistaken)
-resized the system.ext2 to be a multiple of 16. It is now 224mb instead of the 230 it used to be. results: system is speedier...
-warren has updated his kernel again 424 (Changelog to come when he wakes up)
-cyanogen did some work on gps we included in this build and it broke our ****
-cyanogen mod changes from april 23 to april 25th
04/23/11 - UPDATE
-cyanogenmod changes from 04/22 to 04/23
-updated BT audio.conf to attempt AVRCP capability
-engaged more backend WiFi Calling functionality(it's coming along folks)
-introduced cm's mobile data interfaces(thanks for the indirect reminder in git Chas)
[B] AmCanAndroid Kernel v424 - Presented by Warrenb213:[/B]
-updated bcm4329 driver to latest aosp, then modded it a bit(thanks Tytung for a working reference)
-updated netfilter
04/22/11 - Update 1:30PM
-cyanogenmod changes from 04/18 to 04/22
-decreased a sleeptimer from 30sec to 7 seconds in rilwrapper to decrease time between reconnecting data (testing stages.. so far so good for results)
-added a function to automatically inject ISP based dns entries into build.prop
appears to have stabilized data a bit more. (ACA!)
-warren has removed the low bat fix from his kernel for now (was causing issues with wireless bt devices being able to connect
-updated wifi tether apk in /system/app & v3pre tether in /android/androidapps
-issues with adhoc networking have been sorted out with the assistance of [B]darkalex[/B]. THANKYOU brother.
-fix_permissions script now runs for ALL users (partitionedSD or not) when updating to a new build (if you follow the update instructions you will have no problems and this will run automatically) - you will not see it run FYI.
-swype down action in homescreen via adw is working again
[B] AmCanAndroid Kernel v4.20 - Presented by Warrenb213:[/B]
[strike]power drain @ 60mah fix(thx tytung and chastarin)[/strike] [I](removed for now - users reported connectivity issues with some bluetooth enabled devices.)[/I]
updated battery parameters temp reading(thx linux-on-wince team)
Added 2300mah extended battery support(thx Arne182)
fixed AC charging on boot and cleanups(thx Markinus)
04/18/11 - UPDATE:
-cyanogenmod changes from 04/13 to 04/18 -- (sorry those that got the early 18 release the following was not in it... redownload ;) )
- [B]A Present from Warren: Kernel AmCanAndroid r4.18[/B]
04/13/11 - UPDATE:
-freeze on shutdown. (hopefully have this solved)
-minor work done to rootfs and data files
-cyanogenmod changes from the 11th to the 13th.
-evo1rs has done EXTENSIVE testing on the video camera. we have made adjustments based on his findings. ([B]NOTE we are enabling HD 720 recording for you but currently it is only working @ about i think evo1rs said 1.5 frames a second ;/ but all the current modes that you have will work much smoother and better in quality then before. really really good work evo1rs [/B])
[B]-we no longer require 2 seperate builds. 1 for all. :)[/B]
04/11/11: Update
-cm updates from april 10 to april 11
-adhoc functionality added via modified source code
thanks to daveba for the suplicant v6 patch found @ [url]http://forum.xda-developers.com/showpost.php?p=7711198&postcount=6961[/url]
04/10/11: Update
-cm updates from april 8 to april 10
-bkup2sdext working again (all issues resolved)
-pretty much this will be the best build to date we've released. ;) YAY!
04/07/11: Update
-ka_GE local has been added by the cm team
-cm updates from april 6 to april 8
-major changes made ppp/data (changes were found on cyanogen dl mirror in the leo section - not really sure who's to thank for this as there was no names attached.. but i assume someone on the cm team spent some time on our device. so thankyou to them.. and if not then to whomever is responsible. !!!)
-various other changes to init.d files
-test the video recording settings, I updated the media_profiles.xml file, this should allow for higher quality recording (this is new and untested)
-updated a firmware file we were missing (this may not effect anything at this point)
04/06/11: Update
-lots of cyanogenmod updates from April 2 to April 6
-more work done on data to improve data freeze. also incorporated (for testing) a new reconnect method pointed out by xda user [B]nygmam[/B]. [B][U]THANKYOU nygmam![/U][/B]
04/02/11: Update
-cyanogenmod updates from March 29th to April 2
-updated rootfs (new adb binary, various other changes to make our rootfs more closely match cyanogenmod's rootfs)
03/29/11: Update
-cyanogenmod update from march 26 to 29th
-updated boot animation thx evo1rs ;) nicely done
-did some more work on data... positive results so far.
-added SD Card fix speed read fix. All credit for settings adjustment goto [B]xda user brainmaster[/B]. Details found here: [url]http://forum.xda-developers.com/showthread.php?t=1010767[/url]
03/26/11: Update
-cyanogenmod upates from march 20 to 26th :) lots
-removed news section from main post
-added "installation and updating" section to main post
03/20/11: Update
-cyanogenmod7 updates from mar19 to mar20
-fixed previous builds voice search issue
03/19/11:
-cyanogenmod7 updates from Mar 17 to Mar 19th.
-updated busybox to version 1.18.4 (compiled by copenhagen)
03/17/11: - Update
-cyanogenmod7 upates from march 14 to march 17
03/14/11:
-reimplemented data fix (gone since march ~8th meh!)
-cyanogenmod updates from march 12 to 14
-added new section for forum ([url=http://forum.xda-developers.com/showpost.php?p=11417885&postcount=3]post 3[/url]) for user modifications.
03/12/11:
-cyanogenmod updates from march 9 to 12th.
as cyanogen has been making several changes each day, it is still a worthwhile update.
-bkup2sdext re-enabled by default for magloader users.
-included widescreen camera to test [B](copy sdcard/android/CAMTEST/root to sdcard/android/HERE so you see /sdcard/android/root and reboot) THX JHB!![/B]
-at the moment all other existing issues (tho very few exist) are either out of our control, or bound for greatness with the next kernel update from warren
03/10/11:
-cyanogenmod updates from march 8 to 9th.
as cyanogen has been making several changes each day, it is still a worthwhile update.
-no other changes at this time ;) this is nice to see actually. thankgoodness.
-at the moment all other existing issues (tho very few exist) are either out of our control, or bound for greatness with the next kernel update from warren (not yet tho ;)) - which is a good place to be at with any build.
-users already on 030811 can update like normal just copy all new build files to sdcard. and boot.
03/09/11: UPDATE!
-cyanogenmod updates for last 48 hours
-included wifi tether v3 experimental build
-made change to location of wifi tether apk to correct install issues now located in /android/androidapps to be installed on first boot
(we've done this before with wifi tether and it worked) if not other fix still applies*
-reintroduced gsm(2g) fix into build
03/08/11: UPDATE!
-RTL support i hear is now working.. please provide feedback! (my friends in the east, I hope you are still with us! is it really working??)
-major cyanogenmod updates from march 5 to 8th
-new kernel from warren
-wifi should now show hidden networks
-bt quality should also be improved
-gps smooth as silk now
-overhauled data to sd-ext feature
-avrcp still notworking
-decreased boot time with new backup2sdext feature (except first boot)
-fixed voice search function.. (solution was to compile libaudio.so from AOSP instead of CYANOGen GIT)
-reports from users that RTL is now working..... would appreciate more feedback on this please
03/05/11: Update!
-RTL support i hear is now working.. please provide feedback!
-version update from 2.3.2 to 2.3.3
-major cyanogenmod updates from march 1 to march 5th
-work done on avrcp, early tests suggest not working tho
-added cleanup feature to tend to various tasks
move androidapps/* to /backup/app
move android/root to android/.root
remove .rec files from /
03/01/11:
-new kernel (by the one and only WarrenB) AmCanAndroid r3.01
(not sure whats exactly been updated in this baby.. but Warren can update the OP with the details for you) Um YAY!
-Major Major Cyanogenmod Updates from Feb 26 to March 1st
-more work done on bkup2sdext to guarentee no loss of data
-camera fix included in the build, you dont have to do it yourself.
(and THANKYOU for providing what I needed in order to go ahead with this fix you know who u are)(who gets the thanks for bringing this to our attention?)
-removed some useless files - remnants of earlier builds no longer being used.
-removed button savior.. you can get it from the market
-further tweeking on data has done to again increase reliability of the data connection
-as far as I can tell the rogue data on problem is gone
2/24/11c:
-cyanogenmod updates from feb 24 to feb 26
-build now prevents bkup2sdext enable for anyone using magldr rootfs.img
-more data stability work has been done.. improvements seen again
-wierd data auto reconnect bug gone now.. (not sure what was causing it... ah well gone now)
-cyanogenmod updates from feb 24
various updates inc: mms systemui systemsetup framework and improved italian support
- cyanogenmod updates from feb 21st to 24th
- added missing gps files (sorry bout last time)
- added data to bkup2sd so now all user data and app settings are saved to sd-ext ;) (partitioned sdcard users)
- added solution to my senario 4. now uninstalling an app normally uninstalls it from sd-ext partition on device shutdown. ;) so try not to pull your battry if you just uninstalled some stuff, otherwise it will be back when you reboot as the device didnt go though a proper shutdown.
- adjusted the timer on the data reconnection from 3 to 4 seconds. hopefully wont be short enough to not get annoying, but long enough to let the connection completely die before rebuilding it. (blah blah geek speak.... i am playing with data... you probably wont even notice anything!)
2/21/11:
- (partitioned sdcard users only)
NEW app & dalvik-cache auto backup to sd-ext (early stages EXTREMELY
promising !! - this replaces app2sdext feature introduced in feb 11 build.)
if you lose your data.img or format your fat32 partition or upgrade your build. (will work for this build # and moving forward)
all your apps and their program files, all data from your dalvik-cache, is all restored on first boot. (first boot will take some time) this restores the speed of prior to aps2sdext, but now works for us instead of against us
- Fixed Voice Capability
- Docent has updated is swap partition feature (partitioned users only)
- New kernel. WarrenB r2.21
- UTF8 & tun working again.
- cyanogenmod7 RC1 updates from Feb 16 to Feb 21
- Much Much faster then prior release. an HD2 on crack.
- warren's data fixes are still holding up. best data functionality in an android hd2 build we've ever seen.
- [B]we both recommend installing setCPU to extend battery life. (we do NOT recommend changing ANY settings at all. Set to interactive and walk away.[/B])
- thats all i can think of for now.
02/16/11
-cyanogenmod updates from feb 4 to feb 16. inc version update to CM7 RC1.
-kernel updated to v2.9
-ppp fixes (warren) compiled from source (cope) to bring you the best SD PPP build to date for the HD2.
-building process refined ten fold. much cleaner.
-apps2sdext* added. [B]only effects users with a partitioned sd card[/B].
*your apps can essentially survive fat32 partition corruption & format /(and or) data.img loss) makes for updating builds a DREEEEAM!.
Users w/o partitioned sdcards dont worry just proceed as you always have.
-all other features carry over from WarrenBread and Cope's SD builds.
working:
gps, bt (no AVRCP yet), wifi, data 2G(with reconnect after call as it should be), data 3G(no dropped data on call or end call), camera & video camera.
02/14/11 - o.m.g! supersecret internal build
02/11/11 - internal test build
02/09/11 - loyalty build iii
02/05/11 - loyalty build ii
02/01/11 - loyalty build i[/color]
Click to expand...
Click to collapse
Click to expand...
Click to collapse
1 2 3 4 5 6 7 8 9 blah
Post 4 secured.
this is all i need to keep me satisfied
Clarifications based on my limited, early experience with this ROM:
1. "LED me know BETA" app is required to correct the notification LED behaviour.
2. The "TMoUS" build appears to only be for actual subscribers to the T-Mobile USA network. If you have an unlocked HD2 that has the "T-Mobile" logo stamped on the top, but are using it on a different/foreign carrier (like me), you'll want to use the "STANDARD" build.
These aren't complaints. They are just the things I had to figure out in order to get this build running perfectly. Many thanks to Cope and Warren!
Alright new built release!!! thank you guys been waiting on this one!
Wooo New ROM thanks guys
*double win* and i made the first page
Thanks Guys! im on it!
Whaoooh some fresh meat for dinner today!!!!!!!
Thanks guys
Thank you all for your hard work. Hope battery life is good.
copenhagen said:
@question of will i need a new data.img?
probably not. however.. nudge nudge... this wouldnt concern you if you had your sdcard partitioned for apps2sdext
Click to expand...
Click to collapse
From Cope's old thread... do you know if that is confirmed or not?
Thanks! Works fine for me (with "LED me know").
JustX said:
From Cope's old thread... do you know if that is confirmed or not?
Click to expand...
Click to collapse
I used my old data.Img and everything works fine.
Sent from my HTC HD2 using XDA App
I did find a problem with camera set to 'front' when I tried to record a movie. Adding to FAQ
docent14 said:
I did find a problem with camera set to 'front' when I tried to record a movie. Adding to FAQ
Click to expand...
Click to collapse
AHAHHA i beat you docent... check the old thread.. i posted @ you a couple of hours ago
AmeriCanAndroid said:
AHAHHA i beat you docent... check the old thread.. i posted @ you a couple of hours ago
Click to expand...
Click to collapse
Yes, I am reffering to your post exactly. I'll give you the credit, don't worry
My download is taking forever. Anybody using this already to prove/disprove Cope & Warrens assertions. Just hoping the user experience is exactly as stated during the countdown to this rom. Guys dont blame me. You raised the expectations so we will hold you to your word. And of course donate a crate of beer whichever way it goes......
Thanks for everything!
I can´t wait afternoon to try it out!
old data do the work in the new build?
some experience, except jhono235?
All the best!
//not important
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KitKat), which is designed to increase performance and reliability over stock Android for your device.
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What are Nightly builds? Auto compiled builds of the latest CyanogenMod source from github. This version change each night and aren't officialy supported. If you find bugs/issues you can/must discuss here (do not submit nightlies bug on CyanogenMod issue tracker).
All bug reports that don't meet this conditions will be ignored:
You have the kernel provided in the zip file
You made a clean flash and didn't restore anything
You made a detailed review of the problem
You provide a logcat in a .txt file (Search internet)
You provide dmesg or last_kmsg if it is a kernel panic (Search internet)
What's working :
Booting
RIL and Mobile Data
Dual-Sim
Storages (Internal and External)
Notification Led
Flashlight
Sound
Wi-Fi
Bluetooth
GPS
Tethering (BT, Wi-Fi, USB)
Sensors
Video playback
Camera
Browser
What's not working :
NFC (causes instability)
Fm Radio
Cpu Governors SmartassV2 and H3 causing instability
Other stuff that is not here
I DO NOT RECOMMEND USING CM CAMERA (it can stuck and you need to restart); USE OpenCamera INSTEAD!!!
Care with volume. Lower until no cracking sound is present
Instructions :
Reboot to the latest TWRP/CWM/Philz
Make a full wipe (/system, /data, /cache, /dalvik-cache, /internal storage)
Flash the CM11 zip
Flash the four_button.zip (if you have dual)
Make factory reset
Reboot to system
Flash Gapps (if you want) => you need to test which work. Flash pico please or you will have crashes. You need to test this. FLASH ONLY AFTER FIRST BOOT
You can also flash Gapps before booting (after CM11) but if you know how to skip initialization screen (the clockwise press trick). If you don't know what I am talking about, don't ask use the flash after first boot method.
You will not have a setup wizard because I am using INIT to set device model. Please use settings to set up your stuff.
Downloads :
ROM:
cm-11-20160306-UNOFFICIAL-vee7-RC3.zip
md5: 95b61238767d250a06891461ef4a7882
four_button.:
four_button_RC3.zip
md5: 0c03597aa15338f1362c26d44f52d5d6
Credits :
@Dazzozo
@luca020400
@skyinfo
@weritos
@Caio99BR
@Kra1o5
@fonz93
TeamHackLg
CyanogenMod
Xda for this nice home
Donators (BIG THANKS!!!) :
@vlmaxx
The source code is entirely available here: https://github.com/Cyanogenmod11-vee7
XDA:DevDB Information
NCyanogenMod 11, ROM for the LG Optimus L7 II
Contributors
neutrondev
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod 11
Version Information
Status: Beta
Created 2015-06-12
Last Updated 2015-06-12
Reserved
Changelog:
RC3(06-03-2016)
Fm needs to much work and I don't have time; reverted that
reverted overclock causes problems
removed kernel stuff that caused instability
visual performance should be better now
removed hwcomposer
removed vsync ( we don't support that )
added headphones image when headphone is plugged
added the flashlight thing in drop-down menu
fixed blue video in camera
RC2(27-02-2016)
Initial commits for FM radio
Kernel changes:
fixed memory leaks in ext4
improved ext4 speed
added frontswap
limited max readahead to 1MB
improved response of the UI
added sio, sioplus, bfq, fiops, row I/O
changed default I/O to sio (best for our device)
dynamic read-ahead support
3 times faster integer SQRT operation
frandom entropy (way faster then urandom)
removed useless 320 KHz freq from CPU (more aggressive scaling, to be more responsive)
overclocked to 1036 GHz
Enabled ZCACHE
Enabled ZRAM
RC1 (26-02-2016)
reworked device tree, kernel tree entirely
now all is united under vee7
baseband search to set version
camera now compiled from source (focus while in video mode works); the restriction is still clear. no pause on videos
speed should be improved
battery drain should be gone
dual sim most likely fixed (needs confirmation)
enabled ZRAM
enabled ZCHACE
Beta 2 (19-06-2015)
[fixed] Browser
[fixed] Camera
[fixed] GPS, was not locking right
[observed] Battery drain
Beta 1 (12-06-2015) -> not public
[fixed] entire sound
[fixed] browser crash
[added] dual-sim support
[updated] RIL area
Alpha 2 (11-06-2015) -> not public
[fixed] internal storage
[fixed] part of sound
[fixed] flashlight
[working on] camera
Alpha 1 (08-06-2015) -> not public
Initial bringup
Reserved
Frequently asked questions (FAQ) and Instructions:
QUESTIONS AND ANSWERS:
1. How to enable Developer Option?
Go to Settings->About phone->Build number->Tap on it 7 times.
2. How to enable USB Debugging?
After you enable Developer Option go to Settings->Developer options->Check USB debugging.
3. How to enable Reboot recovery from the reboot menu?
Go to Settings->Developer options->Check Advanced reboot.
4. How to disable Home key unlock (it is enabled by default)?
Go to Settings->Buttons->Uncheck Home button wake.
5. Do you want faster UI?
Go to Settings->Developer options->Scroll down to DRAWING->Set Transition animation scale and Animation duration scale and (Optional: Windows animation scale) to Animation scale .5x
You are reworking it from source or it's werito's port just edited?
tomcis147 said:
You are reworking it from source or it's werito's port just edited?
Click to expand...
Click to collapse
As I said this is my last project. It contains my source.
Finally
Good work
Thank you for this final effort. And thank you for the TWRP 2.8.6.0(doesn't flip the screen on reboot anymore).
I'll be sure to try your CM11 rom once I'm out of university for the summer.
This is amazing. Been waiting for CM11 all my life. Good luck in this and in all your future projects neutrondev!
Sent from my [email protected] by neutrondev using XDA Free mobile app
neutrondev said:
As I said this is my last project. It contains my source.
Click to expand...
Click to collapse
I wish there will not be a battery drain the battery is more stable than the cm10.2. Hahahha. Good Luck with this sir.
What you mean with "not working browser" ?
luca020400 said:
What you mean with "not working browser" ?
Click to expand...
Click to collapse
Probly web view framework is not working that renders websites
luca020400 said:
What you mean with "not working browser" ?
Click to expand...
Click to collapse
I am using chromium webview not classic and genlock has some problems. It is a genlock problem that is also related to webview when I will have time I will investigate it
By the way, and it came to me just now, is it possible for you to include the following options?
- turn on/off the annoying "safe headset volume" message
- turn on/off camera shutter sound
- turn on/off heptic feedback(vibration on unlock/hold home key/input pin code when turning the device on)
- custom power off and restart option: reboot/reboot to recovery/reboot to boodloader
Those would be very comfortable for most of us, if not for everyone. Currently on the purified stock v2(KK 4.4.2) i have to use:
- GravityBox(Xposed) for headset volume message and custom restart options
- Open Camera(from play store) because it has an option to mute shutter sound
- Spare Parts to remove heptic feedback(although you can uninstall the app and still have heptic feedback disabled)
My whole point is to have the above mentioned options native to the ROM itself without using third party apps/frameworks.
shhnedo said:
By the way, and it came to me just now, is it possible for you to include the following options?
- turn on/off the annoying "safe headset volume" message
- turn on/off camera shutter sound
- turn on/off heptic feedback(vibration on unlock/hold home key/input pin code when turning the device on)
- custom power off and restart option: reboot/reboot to recovery/reboot to boodloader
Those would be very comfortable for most of us, if not for everyone. Currently on the purified stock v2(KK 4.4.2) i have to use:
- GravityBox(Xposed) for headset volume message and custom restart options
- Open Camera(from play store) because it has an option to mute shutter sound
- Spare Parts to remove heptic feedback(although you can uninstall the app and still have heptic feedback disabled)
My whole point is to have the above mentioned options native to the ROM itself without using third party apps/frameworks.
Click to expand...
Click to collapse
Haptic feedback in stock KitKat need to edit build.prop, in CyanogenMod you can enable and disable in sound settings and lock screen settings. Advanced restart mode in developer options (I think only CyanogenMod, not sure stock roms)
Sent from my p710 using XDA Free mobile app
What are the main differences between this build and @weritos one? In what way it's expected to be better?
doubt
When can we download ?
Wesley Silva said:
When can we download ?
Click to expand...
Click to collapse
You will see when, don't ask for eta.
Build will arrive soon. The thing is that I want to use Chromium Webview (it is new starting from kitkat). Before kitkat classic webview was used. I can use an external classic but I want to update the stuff to work with Chromium one.
Well just some updates. Found time to work today. Camera got fully fixed (Resume now works). I adverted GPS working. Well trying to get a signal it could not lock. That is also fixed now. I just switched to Classic Web View since exams are comming and I see no problems. We can count browser also fixed. Maybe tomorrow is a good day to release an RC already. Will test until then. Peace out.
neutrondev said:
Well just some updates. Found time to work today. Camera got fully fixed (Resume now works). I adverted GPS working. Well trying to get a signal it could not lock. That is also fixed now. I just switched to Classic Web View since exams are comming and I see no problems. We can count browser also fixed. Maybe tomorrow is a good day to release an RC already. Will test until then. Peace out.
Click to expand...
Click to collapse
What exactly are nightly builds? I searched a lot but still not sure how that will work with this rom. Sorry if I'm too dumb and thanks in advance!
Edit: And another question, no battery drain at the moment? (Is not listed in known issues so I guess is fixed or never wasn't there)
Sent from my p710 using XDA Free mobile app
{
"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"
}
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4.x (Kitkat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* 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.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
ROM Downloads
<< Stable >>
20151129 Build: https://www.androidfilehost.com/?fid=24269982087007316
SuperSU Flashable ZIP (needs to be installed separately): https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Previous Releases:
20150816 Build: https://www.androidfilehost.com/?fid=24052804347795005
20150814 Build: https://www.androidfilehost.com/?fi...ww.androidfilehost.com/?fid=24052804347792055
Google Apps (add-on)
https://www.androidfilehost.com/?fid=95916177934548318 <== Avoid to install any Google Apps, but if you really need them this is the recommended package
Installation
3-button-combo = "Volume Up/+" + "Home/Center" + "Power/Lock"
- First time flashing GearCM 11 to your Samsung Wave (or coming from other Android ROMs, including older GearCM releases)?
Download and flash latest available Bada 2.0 for your device (Google will be your best friend in this case)
Download BOOTFILES, Kernel and FOTA for your device
S8500:
BOOTFILES => https://yadi.sk/d/KhxqKyg4bP2nu
"start" kernel => https://drive.google.com/file/d/0B-2dpW_lpZCPNWtxVnRVdUVTcVE/view?usp=sharing
FOTA => https://yadi.sk/d/OtpVoaXpfNggE
S8530:
BOOTFILES => https://yadi.sk/d/cBPD41VEbP2od
"start" kernel => https://drive.google.com/file/d/0B-2dpW_lpZCPT0VCS0tINHU5cnc/view?usp=sharing
FOTA => https://yadi.sk/d/-WnbHbFHfNgZK
Flash BOOTFILES, "start" kernel and FOTA using Multiloader
After Reboot device will automatically boot into recovery
Follow this procedure: Advanced -> Terminal Command -> Select -> Type "sh partition.sh"
Wait until on screen you see "Partitions had been prepared"
Follow this procedure: Back -> Back -> Back -> Reboot -> Recovery -> Swipe to Reboot
After Reboot, device will boot again into recovery
Now you can copy GearCM Flashable ZIP & SuperSU into Internal or External Storage using MTP (Internal/External) or using USB Storage (Only External) <= Check if USB Storage/MTP is enabled in "Mount" menu.
Install the ROM from Internal/External Storage (via "Install" menu)
Wait for about 10 minutes until "Reboot System" button is showed
Install SuperSU from Internal/External Storage (via "Install" menu)
Optionally install Google Addon ("Go Back", "Install"....)
Done! You can now reboot the phone to enjoy the rom
- Upgrading from another build of GearCM 11? (not valid if upgrading to 20151129 build)
Reboot into Recovery using 2-button-combo [Volume Up + Power/End]
Do a Nandroid Backup!
Install the ROM from Internal/External Storage (via "Install" menu)
Wait for about 10 minutes until "Reboot System" button is showed
Install SuperSU from Internal/External Storage (via "Install" menu)
Wipe Dalvik & Cache.
Done! You can now reboot the phone to enjoy the rom
Differences from Standard CyanogenMod
ROM & Kernel are compiled using newest sources and improvements
Removed Useless and RAM-Hungry apps such as VoicePlus & CMUpdater
Optimized Dalvik VM for low-ram and uniprocessor devices
Optimized system DBs access (SQL Optimizations)
System & Userdata partitions are using F2FS instead of EXT4 to get maximum performance from NAND Storage
Device Tree and Kernel have been enhanced and corrected in order to obtain maximum performance from our device
SELinux has been disabled to avoid issues
Pre-Odexed to reduce first boot time
Removed TV Out support (RAM-Hungry and hacky)
Many other performance improvements that i don't remember
Known Issues (regarding latest available Stable build)
Please do not report bugs if it is already listen in the list of known issues
Built-in Sound Recorder crashes if File Type is set to WAV (seems CM sources bug)
Bad Call Quality while on 2G (GPRS & EDGE) Networks (probably related to AMR_WB)
Dynamic Switching between 2G (GPRS & EDGE) & 3G (UMTS & HSDPA) doesn't work (it is recommended to use 3G Only mode)
Rarely, some SIM Cards won't be able to register any network
GPS isn't 100% reliable due to experimental implementation
Conference Calls feature doesn't work yet
Reporting Bugs
You are allowed to report bugs only in this thread. Before reporting a bug, please make sure you are running as stock as possible. This means no custom kernel, no custom framework modification, etc. If you are using any of the above modifications, please flash the rom again to get rid of the modifications before reporting.
REPORT BUGS IN THIS THREAD ONLY
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. The following is a useful format to follow. Note: If you can provide the latest night/build that the bug didn't exist, it would greatly help in tracking down what caused it.
Code:
What is your--
Phone model:
Radio (baseband) version:
GearCM version:
GearCM download url:
Google Apps version:
Did you--
wipe data/factory reset:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
CMSettings/Performance Settings (other than stock):
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Changelog
20151129:
CLEAN INSTALL (first procedure) REQUIRED
Updated CM Sources
Switched to CM12.1 boot animation
Improved Performance here and there
Fixed Dialer issues
Restored some little animations
Reduced RAM Usage
Optimized KSM (still not enabled by default)
Removed useless buttons backlight option
Added GearCMParts to manage mDNIe Screen Options
Switched to ondemand CPU Governor to avoid performance issues
Improved Boot Time
Removed useless notification lights path to Lights HAL (probably cause of memory leaks)
Added Regulatory Info (SAR) to Settings app
Enabled screen dim to save battery
Optimized RAM management for low-ram devices
Restored Themes support
Fixed SetupWizard with Google Apps
"start" kernel: updated to latest version with new GearRecovery base
RECOVERY: switched to new GearRecovery base, newer and with better UI. TWRP Based
KERNEL: added lots of updates to fix memory leaks and minor issues
Previous Releases:
20150816:
Fixed Random Shutdowns when Battery Temperature is too high
Improved Performance & Smoothness
20150814:
Fixed Random Reboots
Improved Performance & Smoothness
Reduced RAM Usage (just a bit)
Disabled KSM by default
Improved Screen-On/Screen-Off latency
20150811:
First Release
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
[GearCM][NAND|S85xx][4.4.4] Optimized CyanogenMod 11 for Samsung Wave I/II, ROM for the Samsung Bada OS
Contributors
Alberto96, Volk204, Rebellos
Source Code: https://github.com/GearCM
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Version Information
Status: Stable
Current Stable Version: 20151129
Stable Release Date: 2015-11-29
Created 2015-08-11
Last Updated 2015-11-30
Reserved
Reserved
Great Job Alberto!
Will try to install on my wave soon)
volk204 said:
Great Job Alberto!
Will try to install on my wave soon)
Click to expand...
Click to collapse
Thank you, it's a pleasure for me that you try my rom
If you find something that needs to be enhanced/fixed, let me know
Great man , testing .......
thank you
thank you man i just install it istead of 5.1
(wave 2 s8530)
setting crash when entering THEMES: theme-pack bootanimation icons font sound-packs
i really hope to get them work in other versions
sound recorder crush when using wav extention
when i choosed wallpaper system restartbut it continue to work normal
apps working fine and very smooth like no other rom (and tried every rom in forum) :good:
as first release it is great can't wait for other releases
ps: i didn't use gapps when i used it went a liiiitlle laggy but not bad
I'm using wave 1 ( gt-s8500)
clean install with no Gapps
-this is maybe be a random bug but when system booted for the first time , i Signal lost and phone rebooted , than shutdown it self ??
nothing when executing
Code:
/proc/last_kmsg.
/system/bin/sh: cat: /proc/last_kmsg: No such file or directory
Click to expand...
Click to collapse
-I took a logcat for this
DIRAR11 said:
sound recorder crush when using wav extention
when i choosed wallpaper system restart but it continue to work normal
Click to expand...
Click to collapse
-i noticed this line in logcat that probably isn't related to the above reported issue
Code:
E/audio_a2dp_hw( 957): adev_set_parameters: ERROR: set param called even when stream out is null
-Some error in media scanner , i checked the files ,and they are corrupted on my sd card
E/MediaScannerJNI( 1333): An error occurred while scanning file '/storage/sdcard1/music/11 - Hooverphonic - Jackie Cane.mp3'.
E/MPEG4Extractor( 957): No width or height, assuming worst case 1080p
Click to expand...
Click to collapse
-When installing the ROM i noticed this 2 lines in the log :
mount: failed to mount /dev/lvpool/userdata
/data: device or resource busy
Click to expand...
Click to collapse
is it related to using F2FS , and there is no reason to worry about
- in anycase the ROM is amazing , very fast comparing to Omni 4.4 ;
Thank you :good:
DIRAR11 said:
thank you man i just install it istead of 5.1
(wave 2 s8530)
setting crash when entering THEMES: theme-pack bootanimation icons font sound-packs
i really hope to get them work in other versions
sound recorder crush when using wav extention
when i choosed wallpaper system restartbut it continue to work normal
apps working fine and very smooth like no other rom (and tried every rom in forum) :good:
as first release it is great can't wait for other releases
ps: i didn't use gapps when i used it went a liiiitlle laggy but not bad
Click to expand...
Click to collapse
1) Themes support has been removed.
2) Sound Recorder doesn't work on my Galaxy S4 too with WAV format, so i'm starting to think that it is an app's bug.
3) Working fine here
ice_ice said:
I'm using wave 1 ( gt-s8500)
clean install with no Gapps
-this is maybe be a random bug but when system booted for the first time , i Signal lost and phone rebooted , than shutdown it self ??
nothing when executing
Code:
/proc/last_kmsg.
-I took a logcat for this
-i noticed this line in logcat that probably isn't related to the above reported issue
Code:
E/audio_a2dp_hw( 957): adev_set_parameters: ERROR: set param called even when stream out is null
-Some error in media scanner , i checked the files ,and they are corrupted on my sd card
-When installing the ROM i noticed this 2 lines in the log :
is it related to using F2FS , and there is no reason to worry about
- in anycase the ROM is amazing , very fast comparing to Omni 4.4 ;
Thank you :good:
Click to expand...
Click to collapse
1) Uhm...this is interesting. Unfortunately i can't test SIM Card because i only have a secondary Micro SIM.
2) Oops...seems that i forgot to enable last_kmsg support in kernel
3) This error:
Code:
E/audio_a2dp_hw( 957): adev_set_parameters: ERROR: set param called even when stream out is null
is normal. It is a fake error.
4) It's normal, because files are corrupted
5) That's another fake error.
You're welcome
Alberto96 said:
You're welcome
Click to expand...
Click to collapse
No; thank you
I only used this ROM for a couple of hours , but i think it is the best one at the moment .
ice_ice said:
No; thank you
I only used this ROM for a couple of hours , but i think it is the best one at the moment .
Click to expand...
Click to collapse
And new version is coming, probably tomorrow, with more performance and fixes.
Sent from my Nexus 4 using Tapatalk
This ROM is s h i t, s h i t
With this ROM the phone is turned off at every turn
When an application apk is installed manually or when installed using the google store, to after open application the phone goes off
Not so with a single application, it happens with many applications.
Too many restarts every few minutes.
I am grateful job to any developer, but to make rom full of mistakes failure is better to do nothing.
I lost my time installing and uninstalling your rom
tofifo said:
This ROM is s h i t, s h i t
With this ROM the phone is turned off at every turn
When an application apk is installed manually or when installed using the google store, to after open application the phone goes off
Not so with a single application, it happens with many applications.
Too many restarts every few minutes.
I am grateful job to any developer, but to make rom full of mistakes failure is better to do nothing.
I lost my time installing and uninstalling your rom
Click to expand...
Click to collapse
It's nice to see someone spamming on XDA, almost every thread on XDA has at least one spammer, so this isn't uncommon to me.
Thank you then, your congratulations are appreciated
Sent from my Nexus 4 using Tapatalk
tofifo said:
This ROM is s h i t, s h i t
With this ROM the phone is turned off at every turn
When an application apk is installed manually or when installed using the google store, to after open application the phone goes off
Not so with a single application, it happens with many applications.
Too many restarts every few minutes.
I am grateful job to any developer, but to make rom full of mistakes failure is better to do nothing.
I lost my time installing and uninstalling your rom
Click to expand...
Click to collapse
Blame your ignorance
"this is a fresh and green teenager comment on youtube . go there for your people , you can understand each others "
Wow! Very nice to see that there are still people willing to dedicate their time to these kind of projects (making a ROM for Samsung Wave is not something that will reach a big audience...).
I have a great respect for you, Alberto96! And also for ice_ice, who keeps giving support for everyone around here (I think he's the only one helping the noobs, such as myself).
I am quite curious to try this ROM, but my question is: is there any chance a SD-ROM version will be released? I am currently using Omni 4.4 from my SD card, which is working fine. I like to keep Bada for emergencies, since many times I found myself traveling somewhere with 2G-only, and in those times Android on Samsung Wave has tons of problems (signal is bad, call quality is bad, etc...). So Bada comes to the rescue.
Anyway, if it's too much trouble porting it to SD-ROM, I might also take a chance with this NAND version, but I just thought I should ask first...
ZephonWave said:
Wow! Very nice to see that there are still people willing to dedicate their time to these kind of projects (making a ROM for Samsung Wave is not something that will reach a big audience...).
I have a great respect for you, Alberto96! And also for ice_ice, who keeps giving support for everyone around here (I think he's the only one helping the noobs, such as myself).
I am quite curious to try this ROM, but my question is: is there any chance a SD-ROM version will be released? I am currently using Omni 4.4 from my SD card, which is working fine. I like to keep Bada for emergencies, since many times I found myself traveling somewhere with 2G-only, and in those times Android on Samsung Wave has tons of problems (signal is bad, call quality is bad, etc...). So Bada comes to the rescue.
Anyway, if it's too much trouble porting it to SD-ROM, I might also take a chance with this NAND version, but I just thought I should ask first...
Click to expand...
Click to collapse
No sorry, I don't have enough time to make two versions.
Sent from my Nexus 4 using Tapatalk
*Mr alberto96 , i tested the ROM with Opengapps . and you may recommend not installing it at the moment . device get short on RAM . and if you just stressed it a little ; apps will crash
I took a logcat while playing with apps and stressing them to crash ,
*i disabled the services not needed in Google play service ;( like fitness and ads ..... ) . more than 150 services that made the wave slow down
*i disabled KSM ; and there is slightly better performance (Less work on CPU )
Here are some interesting line from the Logcat :
-Log has many ANR and APPs not responding
[
Code:
E/ActivityManager( 434): ANR in com.android.systemui
E/ActivityManager( 434): PID: 499
E/ActivityManager( 434): Reason: Broadcast of Intent { act=android.intent.action.TIME_TICK flg=0x50000014 (has extras) }
E/ActivityManager( 434): Load: 14.51 / 9.76 / 5.41
E/ActivityManager( 434): CPU usage from 0ms to 56196ms later:
E/ActivityManager( 434): 9% 2553/com.mxtech.videoplayer.ad: 6.7% user + 2.2% kernel / faults: 6004 minor 198 major
E/ActivityManager( 434): 6.5% 434/system_server: 3.7% user + 2.7% kernel / faults: 6935 minor 183 major
E/ActivityManager( 434): 3.5% 19/ksmd: 0% user + 3.5% kernel
E/ActivityManager( 434): 3.2% 499/com.android.systemui: 2.5% user + 0.7% kernel / faults: 7036 minor 64 major
E/ActivityManager( 434): 2.2% 64/mmcqd/0: 0% user + 2.2% kernel
E/ActivityManager( 434): 1.7% 3031/com.android.vending: 0.7% user + 1% kernel / faults: 3435 minor 132 major
E/ActivityManager( 434): 1.6% 2522/com.google.android.gms: 0.5% user + 1.1% kernel / faults: 4930 minor 382 major
E/ActivityManager( 434): 1.1% 111/rild: 0% user + 1.1% kernel / faults: 25 minor
E/ActivityManager( 434): 0.5% 116/debuggerd: 0.2% user + 0.3% kernel / faults: 1758 minor 213 major
E/ActivityManager( 434): 0.9% 666/com.cyanogenmod.trebuchet: 0.5% user + 0.4% kernel / faults: 2776 minor 33 major
E/ActivityManager( 434): 0.5% 3094/android.process.media: 0.1% user + 0.3% kernel / faults: 2167 minor 71 major
E/ActivityManager( 434): 0.4% 56/irq/121-s5pv210: 0% user + 0.4% kernel
E/ActivityManager( 434): 0.4% 117/surfaceflinger: 0.1% user + 0.3% kernel / faults: 3355 minor 1 major
E/ActivityManager( 434): 0.2% 628/com.android.phone: 0.1% user + 0% kernel / faults: 434 minor 4 major
E/ActivityManager( 434): 0.2% 18/kswapd0: 0% user + 0.2% kernel
E/ActivityManager( 434): 0.1% 6/rcu_kthread: 0% user + 0.1% kernel
E/ActivityManager( 434): 0.1% 15/cfinteractive: 0% user + 0.1% kernel
E/ActivityManager( 434): 0.1% 606/com.google.android.gms.persistent: 0% user + 0% kernel / faults: 447 minor 4 major
E/ActivityManager( 434): 0% 3/ksoftirqd/0: 0% user + 0% kernel
E/ActivityManager( 434): 0% 69/dhd_dpc: 0% user + 0% kernel
E/ActivityManager( 434): 0% 641/com.android.incallui: 0% user + 0% kernel / faults: 332 minor
E/ActivityManager( 434): 0% 770/com.google.process.gapps: 0% user + 0% kernel / faults: 381 minor 4 major
E/ActivityManager( 434): 0% 5/kworker/u:0: 0% user + 0% kernel
E/ActivityManager( 434): 0% 634/com.bel.android.dspmanager: 0% user + 0% kernel / faults: 253 minor
E/ActivityManager( 434): 0% 106/f2fs_gc-254:1: 0% user + 0% kernel
E/ActivityManager( 434): 0% 109/servicemanager: 0% user + 0% kernel / faults: 29 minor
E/ActivityManager( 434): 0% 115/netd: 0% user + 0% kernel / faults: 95 minor
E/ActivityManager( 434): 0% 123/sdcard: 0% user + 0% kernel / faults: 17 minor
E/ActivityManager( 434): 0% 407/flush-254:1: 0% user + 0% kernel
E/ActivityManager( 434): 0% 579/sdcard: 0% user + 0% kernel / faults: 21 minor
E/ActivityManager( 434): 0% 586/com.android.inputmethod.latin: 0% user + 0% kernel / faults: 351 minor 3 major
E/ActivityManager( 434): 100% TOTAL: 15% user + 16% kernel + 65% iowait + 2.3% softirq
Code:
I/ActivityManager( 434): MemInfo: 12952 kB slab, 568 kB shmem, 32 kB buffers, 71792 kB cached, 2616 kB free
I/WindowState( 434): WIN DEATH: Window{421e9798 u0 Keyguard}
I/ActivityManager( 434): Process com.android.systemui (pid 499) has died.
Have a nice day
That's why I say "avoid to install Google apps" 283MB of Total RAM are just enough to run Android.
Sent from my Nexus 4 using Tapatalk
Could you give "call forwarding" and " caller ID" a look . the two were working in CM9 and the earlier builds of CM10 . i don't know what did change
But since then ; Dialer.apk crash when ever you try to access the two in dialer setting
Gapps on 283MB/RAM are for with no question to avoid , even in the days of cm9 when Gapps had less services ;
Kind regards
Thank you so much for this ROM, Alberto! I've been hoping for someone to go back to 4.4 instead of focusing on new features with 5.1 when we dont have enough ram for that and here you are releasing this. Im downloading and installing atm, will report back on the performance.
UPDATE: It seems to run smoothly however, like some people have previously reported, every now and then the phone freezes and restarts randomly as well as when changing the wallpaper. The network works fine (after a few restarts) and we'll see how it performs with use. Also, i keep losing my network connecting after a few minutes of uptime and i have to restart the phone every time that happens.
I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this ROM.
Try this build at your own risk. It's likely to have bugs and is EXPERIMENTAL as it is a work in progress. It boots and seems to work fine on my SM-T350, but I have only tested it for 24 hours. Problems will likley surface later?
BACKUP YOUR FILES and have a copy of your working image BEFORE trying my build.
What works.
1. bluetooth
2. wifi
3. brightness
4. external audio
5. GPS
6. audio through headphone jack
7. Google play store - use pico apps
8. flip flap smart cover
9. audio over bluetooth
Note: first initial boot takes a bit longer, be patient.
Known problems.
1. Home screen text may look fuzzy.
Text on home screen looks funny/fuzzy. This only seems to affect the home screen and nowhere else. I have seen the same problem on the SM-T350, SM-T560NU, SM-P550 and Nexus 7 2013.
Problem is with stock trebuchet launcher and/or its fonts. I tried rootless pixel launcher from fdroid as a quick and simple test and see no problems with home screen text. Rootless pixel uses a different font though. A future LineageOS update could resolve the problem?
Rootless Pixel Launcher | F-Droid - Free and Open Source Android App Repository
F-Droid is an installable catalogue of FOSS (Free and Open Source Software) applications for the Android platform. The client makes it easy to browse, install, and keep track of updates on your device.
f-droid.org
OR you can use nubianprince's crdroid 10.0 build for this tablet. He used his 9.0 repos and has no problems with fuzzy fonts/text. See
[ROM][SM-T350][UNOFFICIAL][crDroidAndroid-10.0][v6.17][ANDROID 10] Galaxy Tab A 8.0
Finally this thread is back :)
forum.xda-developers.com
OR you can use a fairly recent 16.0 build which doesn't have the problem.
2. The stock Jelly browser crashes a lot. Use a different browser. There's lots of better options that are more stable and reliable than the built in Jelly browser.
3. FM Radio is not support since this device doesn't have the LTE functionality.
4. Stock camera does not take picture on front facing camera. Use open camera instead. I don't know when stock camera was broken, but when I tested the March 7, 2021 build, it doesn't work.
Open Camera | F-Droid - Free and Open Source Android App Repository
Camera App
f-droid.org
5. BOE panel
For people who get black or blank screens when trying to flash TWRP 3.3.1 or LineageOS or crDroid SM-T350 roms, it's likely you have a BOE sourced panel.
Code:
adb root
adb shell cat /proc/cmdline
The very last parameter will be mdss_mdp.panel. If you see BOE anywhere in that string, then you have a BOE panel. For example,
mdss_mdp.panel=1:dsi:0:ss_dsi_panel_S6D7AA0_LSL080AL03_BOE_WXGA:1:none
There is a fix as documented at
[ROM][SM-T350][UNOFFICIAL][crDroidAndroid-10.0][v6.17][ANDROID 10] Galaxy Tab A 8.0
Finally this thread is back :)
forum.xda-developers.com
Thanks/Credits
Thanks to @nubianprince and @lividhen99 for ideas and suggestions on getting this build to work. I used one of nubianprince's repos for this build.
FAQ - I spent hundreds of hours building this rom. The least you can do is spend a few minutes reading everything before posting.
Q1) Does the build work on xyz?
A1) I have no idea. I only have the SM-T350. You can try it on variations, but don't be surprised if you get bootloop or bricked hardware. In addition, I won't build it for the 355 (LTE) version.
Q2) Application xyz doesnt' work. Can you fix it?
A2) I only fix what I use. If you use app xyz and it doesn't work, then try 16.0 or going back to the last rom that worked for you.
Q3) My tablet hangs or crashes with 17.1. This build is slow and buggy. Can you fix it?
A3) Go back to the last working stable rom for you. 17.1 is a work in progress and will have bugs and frequent changes.
Q4) Do you plan to update the rom?
A4) Yes as long as I have high speed Internet, I wil try to release the rom monthly to incorporate the security patches.
Q5) What TWRP should I use?
A6) TWRP 3.3.1 or 3.5.0.9. Get it from
https://forum.xda-developers.com/galaxy-tab-a/development/rom-galaxy-tab-8-0-t4158163
Q6) What is the difference between this rom and crdroid?
A6) Use this rom, crdriod or stock. It's not a popularity contest, so use whatever fits your needs. I only offer this as an option for those who want or need a new rom. Most of the code is the same between this rom and crdroid, however, the way we implemented the fixes might be slightly different. In addition, if there is a bug in this rom, it may not be in crdroid due to coding differences and how it's fixed.
Q7) Can I turn off the on screen navigation keys?
A7) To turn off on screen navigation, go to settings, system, advanced, gestures, system navigation, gesture navigation.
Q8) Can I build this rom? Where are the source and kernel source files?
A8) Yes. I have uploaded the repo diff and roomservice.xml file. The kernel source files are at
Samsung MSM8916 Devices
Samsung MSM8916 Devices has 68 repositories available. Follow their code on GitHub.
github.com
The repo diff is what I changed compared to "stock" msm8916 code. The majority of the repo diff is because there's a bug in 17.1 WiredAccessoryManager.java and I reverted back to the 16.0 code. The bug prevents audio through the headphone jack. See
https://forum.xda-developers.com/showpost.php?p=83445681&postcount=13
Q9) Where can I download this rom?
A9) You can find the 2020 17.1 and 16.0 builds at
Downloads for : Samsung Galaxy Tab A 8.0 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I'm moving to sourceforge for all 2021 uploads. The main reason is that I would like to see the stats of where this rom is being downloaded from worldwide. All 2020 builds will remain on androidfilehost.
2021 builds found at
retiredtab - Browse /SM-T350/17.1 at SourceForge.net
sourceforge.net
TODO
1. document and upload long list of fixes you need to build 17.1 if you want on your own.Done.
2. mirror nubianprince's repo in case it gets deleted.Done.
3. upload some files, fixes and documentation to github for future.Done.
Dec 13, 2021 release notes
1. Dec 5 security patches as per https://review.lineageos.org/q/topic:Q_asb_2021-12
2. Whatever LiineageOS changed since last November release (about 4,400 files had to be recompiled).
Nov 8, 2021 release notes
1. Nov 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/318647
2. Whatever LiineageOS changed since last October release (about 5,100 files had to be recompiled).
Oct 10, 2021 release notes
1. Oct 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/317410
2. Whatever LiineageOS changed since last Sept release (about 4,700 files had to be recompiled).
Sept 17, 2021 release notes
1. Sept 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/316083
2. Whatever LiineageOS changed since last August release (about 49,500 files had to be recompiled).
Aug 7, 2021 release notes
1. August 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/314572
2. Whatever LiineageOS changed since last July release (about 4500 files had to be recompiled).
July 12, 2021 release notes
1. July 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/313448
2. Whatever LiineageOS changed since last June release (about 4500 files had to be recompiled).
June 15, 2021 release notes
1. June 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/312240
2. Whatever LiineageOS changed since last May release (about 5400 files had to be recompiled).
May 10, 2021 release notes
1. May 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/309564
2. Whatever LiineageOS changed since last April release.
April 12, 2021 release notes
1. April 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/307454
2. Whatever LiineageOS changed since last March release. Nearly 59,000 out of the 70,000 files had to be recompiled due to the last set of changes.
Release notes for March 7, 2021
1. Mar 5 security patches.
2. Whatever LiineageOS changed since last February release.
3. Stock camera does not save picture on front facing camera. Use open camera instead. I don't know when stock camera was broken, but when I tested the March 7, 2021 build, it doesn't work. I never use the camera or video recording on the tablets.
Release notes for Feb 10, 2021
1. Feb 5 security patches.
2. fixed audio over bluetooth. Huge thanks to @nubianprince for helping with suggestions and his repos. The problem was that some of the audio xml files weren't being copied over in 17.1 because of some directory changes to hardware/qcom.
3. Whatever LineageOS changed since last Jan 2021 update.
Release notes for Jan 14, 2021
1. Jan 5 security patches.
2. Changed some error messages to verbose to stop spamming log files.
3. Whatever LineageOS changed since last Dec 2020 update.
4. For some reason after flashing the rom, TWRP 3.3.1 now says "unable to mount storage". I had never seen that before. Nevertheless, if you reboot, the rom will work fine. I test all my builds before uploading.
Release notes for Dec 14, 2020
1. Dec 5 security patches.
2. Changed some error messages to verbose to stop spamming log files.
3. Whatever LineageOS changed since last Nov update.
4. Add timekeep functionality since SM-T350 has no real time clock. This allows the tablet to keep time when not used with a NTP (network time protocol) server. It works in Android OS and TWRP.
Nov 8 release
- Nov 5 security patches
Oct 8 release
- Oct 5 security patches
Sept 13 initial release
- Sept 5 security patches
- initial release for testing and help fixing bugs
- CPU and GPU overclocked to 1.6Ghz and 650 respectively - built into 17.1 kernel code
- based on stock github MSM8916 T350 code with a LOT of bug fixes and using one of nubianprince's repos
Oct 8 build released. See post #4 for changes.
I set the time to Oct 18 but it was changed to Jan 18 after reboot, then October 9. I remember that crdroid have the same issue.
See this logcat:
Code:
01-18 08:52:10.608 680 680 I SystemServer: StartAlarmManagerService
01-18 08:52:10.611 680 680 D AlarmManagerService: Kernel timezone updated to -480 minutes west of GMT
01-18 08:52:10.611 680 680 I AlarmManager: Current time only 1471930611, advancing to build time 1602188073000
01-18 08:52:10.611 680 680 D AlarmManagerService: Setting time of day to sec=1602188073
10-09 04:14:33.001 680 680 W AlarmManagerService: Unable to set rtc to 1602188073: Invalid argument
10-09 04:14:33.006 680 680 D SystemServerTiming: StartAlarmManagerService took to complete: 10ms
Backlight problem is still in my BOE device. I don’t know which logs are necessary, so I kept most of them. The logs about BOEpanel of crdroid are same with Los, but may be different in other places.
Hope it could be solved.
Which TWRP image are you using? I've seen a couple different ones, but since there's no official support over at http://twrp.me/ I'd prefer to use the same one you're using to test this ROM installation...
Hexrotor said:
The logs about BOEpanel of crdroid are same with Los, but may be different in other places.
Click to expand...
Click to collapse
I'll take a look, but right now I have a big project that I need to get finished by mid November so my time for building and troubleshooting roms is limited right now.
reukiodo said:
Which TWRP image are you using?
Click to expand...
Click to collapse
TWRP 3.3.1
Hexrotor said:
The logs about BOEpanel of crdroid are same with Los, but may be different in other places.
Click to expand...
Click to collapse
These messages
D modemanager: Panel Name: S6D7AA0_LSL080AL03_BOE_wxga_video_mode_dsi_panel
E modemanager: readXMLOp:Couldn't open OEM XML file!
E modemanager: retrieveMode: Failed to enumerate modes
E modemanager: instantiateModeMgr: Failed to update default cache!
E modemanager: readXMLOp:Couldn't open OEM XML file!
E modemanager: retrieveMode: Failed to enumerate modes
E modemanager: in applyDefaultMode fail to retrieve default mode!
I modemanager: in applyDefaultMode ret = 0 mCurMode = -1
are from the proprietary module (which is why I couldn't find them in the AOSP code)
system/vendor/lib/libmm-qdcm.so
If you search for those keywords above, they all appear in this module.
At this time, I have no idea what the libmm-qdcm.so does and how it controls the backlight, if at all.
can someone provide link for twrp 3.3.1 for t350? i just can't find it.
spiramedia said:
can someone provide link for twrp 3.3.1 for t350? i just can't find it.
Click to expand...
Click to collapse
From
https://forum.xda-developers.com/galaxy-tab-a/development/rom-galaxy-tab-8-0-t4158163
TWRP 3.3.1 is at
https://drive.google.com/file/d/14T99LQaKtEhGeglFxrUm0kMRw_RKopP5/view
me t350 just shut's down on his own. clean install.
spiramedia said:
me t350 just shut's down on his own. clean install.
Click to expand...
Click to collapse
Works fine for me and others.
@spiramedia Maybe your device is using BOE panel, try to Illuminate the screen with a flashlight.
Hexrotor said:
@spiramedia Maybe your device is using BOE panel, try to Illuminate the screen with a flashlight.
Click to expand...
Click to collapse
mine is BOE. But i have no problem with this. The tablet just shuts down when using it. Maybe it overheats.
spiramedia said:
mine is BOE. But i have no problem with this. The tablet just shuts down when using it. Maybe it overheats.
Click to expand...
Click to collapse
@spiramedia, when asking for help, it helps us if you provide maximum information. For example,
1) What are you running when the tablet shuts down? High performance gaming? Watching youtube?
2) How long does the tablet run before shutting down?
3) Maybe your battery is really old and weak especially if you used it daily for 5 years?
4) If you think it overheats, you can download several CPU apps that tell you the temperature of the CPU like
https://f-droid.org/en/packages/com.kgurgul.cpuinfo/
5) If the battery is old and weak, does it shutdown when you have the AC microusb adapter plugged in all the time?
6) When it shuts down, what is the battery percentage at?
7) Is your battery guage calibrated properly? If it says 30%, maybe it's really 0% and you have to discharge/recharge 2 or 3 times to recalibrate?
As you can see, I asked a lot of questions. The more info you can give, the better.
PS. If you have a BOE panel and backlight works, then I have no idea why my rom works with yours and not Hexrotor.
Hexrotor said:
I set the time to Oct 18 but it was changed to Jan 18 after reboot, then October 9. I remember that crdroid have the same issue.
Click to expand...
Click to collapse
@Hexrotor, does this happen if you date and time setup to "use network provided time".
If I turn "use network provided time" off, then yes, the tablet doesn't keep time properly. I think it's due to the Qualcomm RTC being read only? Searching the Internet, a possible fix might be
https://github.com/LineageOS/android_hardware_sony_timekeep
I might try incorporating that into the next rom build which will likely be sometime mid Nov when the next security patches are released.
I think it's defaulting to Oct 9 because the build date is Oct 8, but in your timezone, it might be Oct 9.
Hexrotor said:
Backlight problem is still in my BOE device. I don’t know which logs are necessary, so I kept most of them.
Click to expand...
Click to collapse
The error messages for the BOE panel are just before the system stops the boot animation and gives the 3 dots and says LineageOS. I find that to be confusing because I would think the kernel would enable BOE backlight at the very beginning so you can see what is on the display. It makes no sense to have the backlight completely dark and then enable it just before the 3 dots that says LineageOS.
And if spiramedia's BOE backlight works with my rom, then I don't know why it doesn't work with yours. Maybe there is something persistent in one of the persist partitions where a prop is set?
Hexrotor said:
Backlight problem is still in my BOE device.
Click to expand...
Click to collapse
@Hexrotor, you didn't specify in this thread or the original crdroid thread whether you tried downgrading the stock to marshmellow and then try crDroid 10 or LineageOS 17.1.
Apparently, it fixes the no backlight for some people? See
https://forum.xda-developers.com/showpost.php?p=83488241&postcount=41
It's possible the marshmallow firmware has something coded into the file system partitions that fixes the BOE? Maybe someting in the aboot partition?
Let me know if you have tried downgrading or not as per above.
retiredtab said:
Apparently, it fixes the no backlight for some people? See
https://forum.xda-developers.com/showpost.php?p=83488241&postcount=41
It's possible the marshmallow firmware has something coded into the file system partitions that fixes the BOE? Maybe someting in the aboot partition?
Let me know if you have tried downgrading or not as per above.
Click to expand...
Click to collapse
Nope, I tried this way but no help. I flashed marshmallow firmware then Crdroid6.9 without clean, it was no display but heated up at boot. I waited for about 10min but it didn't boot complete. Edit: I tried again just now, it booted successfully but still no backlight. Now I'm using official marshmallow.
I don't know why this ROM works with spiramedia's BOE device. I have some friends who have T350/P350 BOE devices and all they have backlight problem with 3-part ROMs, that’s why I am sure that the backlight problem is related to BOE.
For Los 17 and Crdroid, my device has no backlight after the "Samsung Galaxy Tab A", but official marshmallow works fine.
PLEASE BEFORE YOU decide to try this rom, you MUST read all of post 1, 2, 3 and 4 (about 10 minute read). If you think this is an unreasonable request, then stop reading now and find another rom. Thank you.
I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this rom.
BACKUP YOUR DATA AND OLD rom BEFORE trying my rom.
If you are NOT an expert in using fastboot, adb, odin, heimdall, twrp, DO NOT use this rom. You must know how to use these tools to revert back to your old rom.
If you are new to flashing custom roms, do NOT attempt this.
If you need your tablet for work and something important, do NOT flash this rom. This rom could result in a bricked device or boot loop or non booting device or you not being able to revert back to your old rom.
What works
1. bluetooth
2. wifi
3. brightness
4. external audio
5. GPS
6. audio through headphone jack
7. audio over bluetooth
8. selinux enforcing
9. camera
Thanks
1. LineageOS team for source code.
2. Pre alpha testers for the Samsung Tab A/E roms who provided valuable feedback: lpedia, Schaagi, katochwa, Henrick Grimler
3. nubianprince for helping fix audio over bluetooth on SM-T350 on 18.1.
4. Huge thanks to Henrick Grimler https://github.com/Grimler91 for helping me reproduce a major bug in 18.1 which led me to find a solution. Henrick also helped fine tune some of the sepolicy as well.
5. Sebastiano Barezzi https://github.com/SebaUbuntu for giving the msm8916 repo some 18.1 code updates in March 2021.
6. Exynos5420 team for sharing it's knowledge in building roms.
7. msm8916 team for their repos
8. dylux for suggesting a fix for the front camera photo/record crashing by using stock SM-T350 media_profiles.xml.
FAQ - I spent hundreds of hours building this rom. It was frustrating process from Nov 2020 to March 2021 running into bug after bug. The least you can do is spend a few minutes reading everything before posting.
Q1. Where are the source and kernel source files?
A1. The kernel source files are at
GitHub - Galaxy-MSM8916/android_kernel_samsung_msm8916: MSM8916/MSM8929/MSM8939 kernel for Samsung devices.
MSM8916/MSM8929/MSM8939 kernel for Samsung devices. - GitHub - Galaxy-MSM8916/android_kernel_samsung_msm8916: MSM8916/MSM8929/MSM8939 kernel for Samsung devices.
github.com
The device tree files are at
GitHub - retiredtab/android_device_samsung_msm8916-common: Common MSM8916 tree for Samsung devices
Common MSM8916 tree for Samsung devices. Contribute to retiredtab/android_device_samsung_msm8916-common development by creating an account on GitHub.
github.com
GitHub - retiredtab/device_samsung_gt58wifi
Contribute to retiredtab/device_samsung_gt58wifi development by creating an account on GitHub.
github.com
GitHub - retiredtab/device_samsung_gte-common at lineage-18.1
Contribute to retiredtab/device_samsung_gte-common development by creating an account on GitHub.
github.com
The vendor tree files are at
GitHub - retiredtab/vendor_samsung_msm8916-common
Contribute to retiredtab/vendor_samsung_msm8916-common development by creating an account on GitHub.
github.com
GitHub - retiredtab/android_vendor_samsung_gt58wifi
Contribute to retiredtab/android_vendor_samsung_gt58wifi development by creating an account on GitHub.
github.com
In addition, there is a repo diff file for device specific tweaks needed to work and a roomservice.xml (local manifest file) file so you can build this rom yourself.
Q2. Is this BETA rom suitable as a daily driver?
A2. It can be depending on your requirements. I can't test every app so you try it yourself to see if it's suitable. I've been using this rom myself since mid March 2021 with no major issues.
Q3. What if my app, xyz, doesn't work?
A3. I won't answer questions regarding why your app doesn't work. If your app, whatever it is, doesn't work, then go back to your old rom. It's difficult enough building and maintaining these roms. Remember, I'm an unpaid volunteer making a rom for free for your benefit.
Q4. Your rom is laggy and buggy.
A4. If you find the above, then go back to your old rom. There's only so much software can do on a 2015 budget level tablet. Remember a budget tablet will have the slower SoC/CPU and less DRAM than a top of the line model. Your tablet will also run slower when you use gapps (google apps). You can run a lot of software without using gapps. Research fdroid, newpipe, Aurora store etc.
Q5. What TWRP should I use?
A5. You MUST use TWRP 3.5.2_9. Get it from
[ROM][SM-T350][UNOFFICIAL][crDroidAndroid-11.0][v7.10][ANDROID 11] Galaxy Tab A 8.0
I am not responsible for bricked devices, or any other hardware malfunctions that comes as a result of flashing this ROM, Please do some research if you have any concerns about features included before flashing it, this ROM was built for the...
forum.xda-developers.com
Q6. Why should I use this rom?
A6. You don't. If you don't like this rom, then don't use it. Yes, it's that simple.
Q7. Will you offer monthly updates with security patches?
A7. I will try to offer monthly security patches, but that all depends on if I continue to have high speed Internet in the future.
Q8. Can you help me? I'm a newbie. Can you provide step by step instructions?
A8. Do your own research. There are lots of tutorials, videos, etc on how to flash roms. Newbie questions must be posted in the Questions and Answers forum, not here.
Q9. Can I report a bug with respect to the rom?
A9. Yes, but you need to supply the following information. If you don't, I won't look at it.
You must provide an adb logcat of the problem and tell me how to reproduce it. Note I will not be downloading any apps that require money or an userid/password. For example, if you have problems with Netflix, I cannot help you since I don't have a paid subscription. If you use some app that requires an userid/password, I cannot help you as I'm not willing to create another userid/password even if it's free.
To get a logcat, open up a terminal window.
Code:
# clear the logcat first
adb logcat -c
# start logcat trace
adb logcat > problem.txt
# reproduce problem
# wait until problem has occured, then stop trace by hitting ctrl-c
Q10. Will you still build 17.1 for this device?
A10. Yes, for now, but I will probably discontinue building 17.1 at the end of 2021. I will likely be trying to build 19.0 once it's released so I don't want to maintain 3 releases.
Q11. Do I need to erase everything and format my data?
A11. Yes, you MUST erase all the partitions (system, data, dalvik/art cache, cache) using TWRP and MUST format your data before installing 18.1 when you are coming from stock or an earlier version of LineageOS or from another custom rom. If you get stuck at the boot animation for more than 5 minutes, it's likely because you didn't follow the instructions I just wrote. Dirty flashes from stock, other custom roms or older LineageOS versions are not supported and not likely to work.
Q12. What gapps should I use?
A12. I don't use gapps anymore. I use Aurora Store. As of Nov 6, 2021, I no longer make recommendations on which gapps to use as your mileage may vary. It's reported that opengapps does no testing on their daily builds and some version results in bootloops, bitgapps may run out of disk space will installing apps and Mindthegapps as causing overall slowdown of the system.
The only recommendation I can make is to use the SMALLEST version of gapps which is PICO or equivalent naming convention. DO NOT use anything other than PICO. That is, do not use nano, mini, stock, etc.
If you are going to install gapps, flash the rom first, reboot into system/OS, reboot to recovery, flash gapps, reboot into system/OS. That is, do not flash/install the rom and gapps at the same time.
Q13. I'm having problems with gapps, can you answer why it's not working?
A13. I will not answer any questions regarding gapps. This thread is about the rom, not gapps and I don't use gapps so I cannot help you. Android does not depend on gapps in order to work.
Q14. Why isn't my post answered?
A14. It's probably because it's answered in the FAQ or not relevant to the rom. Again, I do not run Windows OS or use gapps. Questions already answered in the FAQ will be completely ignored.
Q15. Can I turn off the on screen navigation keys?
A15. To turn off on screen navigation, go to settings, system, advanced, gestures, system navigation, gesture navigation. It's enabled by default because I find it useful. If you don't like it, you only need to disable once and your preference will be remembered. If you want to invert the onscreen keys, goto settings, system, buttons and enable invert layout
Q16. What speed up/optimization tips do you suggest?
A16.
1. Turn off animations. Go into developer settings, scroll down to the drawing section, and set window, transition and animator scale all to "off".
2. If you don't have a google account, don't install gapps. Use Aurora Store to get your apps as you can get all the same apps from the play store using an anonymous login.
3. Dont' run more than 2 apps at the same time. You can probably listen to music in the background and use a web browser at the same time, but don't expect great performance from a 2015 entry level tablet.
4. Use a web browser like Brave that has built in adblock and privacy features.
5. Use newpipe to watch your streaming content. It has built in adblock so you don't have to watch forced ads.
6. Look for apps that are open source, ad free and lightweight.
Q17. Does this rom support Magisk?
A17. I don't use Magisk myself so I don't know and Magisk is always being updated to fool Google's certification process. Others have reported Magisk as working, but I won't answer any questions regarding it.
Q18. Will this rom ever become official?
A18. Never. I don't want the responsibilities that come with being an official maintainer. In addition, I know my device trees, code organization and git commits will NOT meet LineageOS standards. Remember, I'm an unpaid volunteer doing this in my free time and sharing my work with you for free so you can get hundreds of hours of enjoyment from this tablet.
Q19. What is the difference between this rom and others?
A19. This rom tries to be pure LineageOS with little to no modifications. Other roms may have different UI, different bundled apps, etc. Use whatever meets your requirements.
Q20. Will there be any major 18.1 code modifications in the future?
A20. I don't anticipate any major modifications. There may be some slight tweaking to the sepolicy, small bug fixes and minor code cleanup, but all the hard work in getting the rom up and running and fixing all the major bugs have been done completed. This doesn't mean the code is perfect or well organized, but I won't be doing any major changes now that 18.1 is working. Any major changes will be done in 19.0.
Q21. Why did you fork the device and vendor trees for 18.1?
A21. The msm8916 repos seem geared towards phones and sometimes do not work or cause boot animation loops for tablets so I decided to fork their repos. In other words, what's deemed as msm8916-common code isn't common to all devices.
In addition, since I'm building SM-T350, SM-T550, SM-P550 and SM-T560NU (all use the same msm8916 code), it seems easier to maintain all of them if I can control my own code repos and not worry if my changes affects the phones or not. I still have not figured out the best way to manage all my repos and it's a work in progress.
Q22. Can you build a variant of this device? For example, a LTE or S-pen version.
A22. If I don't physically have the device, I cannot and will not build it unless I can boot and test it myself. Even then, there's no guarantee that I can get those variant features working.
Q23. Can I load this rom on a variant devivce like LTE or S-pen version?
A23. The rom is built for the device explicitly listed. If you are an advanced user and understand TWRP, adb, odin, heimdall, you can try loading it on a LTE or S-pen variant by modifying the updater-script, but it may cause a bricked device, bootloops or non functionality of LTE/S-pen. You have been informed and warned!
Q24. Will this run on the SM-T355 or SM-P355?
A24. No. Someone has tried and it will result in a bootloop.
Q25. How do I know if I have a BOE panel?
A25. Some ST-350 tablets have a BOE display panel. In order for it to work with TWRP and any custom rom, you must have the correct bootloader installed on a BOE panel otherwise you will see a black/blank screen. To check to see if you have a BOE panel, open a terminal and
Code:
adb root
adb shell cat /proc/cmdline
The very last parameter will be mdss_mdp.panel. If you see BOE anywhere in that string, then you have a BOE panel. For example,
mdss_mdp.panel=1:dsi:0:ss_dsi_panel_S6D7AA0_LSL080AL03_BOE_WXGA:1:none
There is a fix as documented at
[ROM][SM-T350][UNOFFICIAL][crDroidAndroid-10.0][v6.17][ANDROID 10] Galaxy Tab A 8.0
Finally this thread is back :)
forum.xda-developers.com
Q26. What is a GO build?
A26. A GO build uses less DRAM, disk space and supposed to be better suited for devices with 2GB DRAM or less. I have no idea whether it's true or not vs a NON GO build, but I figured I would try a GO build.
Some of the features removed in a GO build are documented in post #46 in this thread in addition to work profiles. If you need these features, you can edit a property in the build.prop as documented in post #49.
Q27. Okay, I understand the consequences and that this is BETA rom and willing to take the risks outlined, now where can I find the rom?
A27. Downloads are at
retiredtab - Browse /SM-T350/18.1 at SourceForge.net
sourceforge.net
NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.
June 9, 2023 release notes
1. June 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-06
2. Whatever LineageOS changed since last May release (about 5,500 files had to be recompiled).
May 7, 2023 release notes
1. May 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-05
2. Whatever LineageOS changed since last Apr release (about 7,200 files had to be recompiled).
Apr 15, 2023 release notes
1. Apr 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-04
2. Whatever LineageOS changed since last Mar release (about 28,000 files had to be recompiled).
March 20, 2023 release notes
1. Mar 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-03
2. Whatever LineageOS changed since last Feb release (about 20,000 files had to be recompiled).
Feb 12, 2023 release notes
1. Feb 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-02
2. Whatever LineageOS changed since last Jan release (about 12,500 files had to be recompiled).
Jan 8, 2023 release notes
1. Jan 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-01
2. Whatever LineageOS changed since last Dec release (about 4,400 files had to be recompiled).
Dec 11, 2022 release notes
1. Dec 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-12
2. Whatever LineageOS changed since last Nov release (about 5,000 files had to be recompiled).
Nov 11, 2022 release notes
1. Nov 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-11
2. Whatever LineageOS changed since last Oct release (about 5,000 files had to be recompiled).
Oct 7, 2022 release notes
1. Oct 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-10
2. Whatever LineageOS changed since last Sept release (about 5,500 files had to be recompiled).
Sept 12, 2022 release notes
1. Sept 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-09
2. Whatever LineageOS changed since last Aug release (about 12,500 files had to be recompiled).
Aug 5, 2022 release notes
1. Aug 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-08
2. Whatever LineageOS changed since last July release (about 4,000 files had to be recompiled).
July 8, 2022 release notes
1. July 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-07
2. Whatever LineageOS changed since last June release (about 1,500 files had to be recompiled).
June 11, 2022 release notes
1. June 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-06
2. Whatever LineageOS changed since last May release (about 9,500 files had to be recompiled).
May 7, 2022 release notes
1. May 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-05
2. Whatever LineageOS changed since last April release (about 11,000 files had to be recompiled).
3. Selfie camera and video no longer crash with stock camera. Thanks to @dylux for suggesting these fixes which are commits
https://github.com/retiredtab/devic...mmit/c9ac11147f83d611e006731aad7c14108f293d64
and
https://github.com/retiredtab/devic...mmit/cfa55e0478b59821f3d16501104b51ceeef8b010
April 10, 2022 release notes
1. Arpil 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-04
2. Whatever LineageOS changed since last March release (about 11,000 files had to be recompiled).
Mar 12, 2022 release notes
1. Mar 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-03
2. Whatever LineageOS changed since last Feb release (about 5,700 files had to be recompiled).
Feb 12, 2022 release notes
1. Feb 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-02
2. Whatever LineageOS changed since last January release (about 34,500 files had to be recompiled).
Jan 20, 2022 release notes
1. Jan 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-01
2. Whatever LineageOS changed since last December release (about 10,000 files had to be recompiled).
Dec 10 release notes
1. Dec 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2021-12
2. Whatever LineageOS changed since last November release (about 11,000 files had to be recompiled).
Nov 7 release notes
1. Nov 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/318560
2. I enabled zram swap with size 512MB. I noticed that the last couple of months that Clash Royale would crash/close and logs showed
Code:
10-28 14:26:01.412 0 0 I [2: kswapd0: 91] lowmemorykiller: Killing 'ell.clashroyale' (6730), adj 0,
Hopefully, by enabling zram, that will stop Clash Royale from crashing/closing.
Zswap is enabled on stock Nougat SM-T350 (part of the Samsung Tab A/E family that uses same msm8916 kernel code)
https://github.com/retiredtab/andro...mmit/2a6bf385e6dfe6073fe328b7b1c563ccd60a5ede
https://github.com/retiredtab/andro...mmit/438d5d3ad20cbc98f0f8c18eb610b6268de19395
This code uses the in kernel low memory killer (lmk). I tried using the Android OS lmk, but it doesn't work very well and shows this in the log.
Code:
E lowmemorykiller: /proc/zoneinfo parse error
E lowmemorykiller: Failed to get free memory!
3. Whatever LineageOS changed since last Oct release (about 7,200 files had to be recompiled). One of these changes has removed the built in terminal program from LineageOS as AOSP deprecated this app as per
https://review.lineageos.org/c/LineageOS/android_vendor_lineage/+/304043
Oct 10 release notes
1. Oct 1 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/317001
2. Added https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/316839 to fix landscape mode system UI. This patch is not yet officially merged as of Oct 10 release.
3. Whatever LineageOS changed since last September release (about 6,100 files had to be recompiled).
Sept 10 release notes
1. Reverted the patch to https://github.com/retiredtab/andro...mmit/a32c7a0bed536281d20b7c1cf8d41c84a268cc80
Removing systemUI from pinner services causes a 4 to 6 delay in bringing up the home screen. This is seen when loading or playing a game for about 20 minutes and then either hitting the recents or home button. By reverting this commit, pressing recents or home button brings up the systemUI right away.
2. Sept 5 security patches as per https://review.lineageos.org/c/LineageOS/android/+/315661
3. Whatever LineageOS changed since last August release (about 6,200 files had to be recompiled).
Aug 8 release notes
1. Fix battery status icon. When you plug in AC adapter, settings, battery does not show it charging even though it is. This is due to the sepolicy being too restrictive. I added https://github.com/retiredtab/msm89...mmit/c1eca9f7740b6a384d4fab8a1e8d812f59c17a99
2. Aug 5 security patches as per https://review.lineageos.org/c/LineageOS/android/+/314477
3. Whatever LineageOS changed since last July release (about 11,500 files had to be recompiled).
4. 18.1 continues to be my daily driver since March 2021.
July 10 release notes
1. Initial public release to XDA. This is an ALPHA build.
2. July 5 security patches as per https://review.lineageos.org/q/topic:"android-11.0.0_r39"+(statuspen OR status:merged)
Reserved.
New build called lineage-18.1-20210718-UNOFFICIAL-gt58wifi.zip
July 18 release notes
1. Fix battery status icon. When you plug in AC adapter, settings, battery does not show it charging even though it is. This is due to the sepolicy being too restrictive. I added
Code:
allow hal_health_default sysfs_charger:dir search;
allow hal_health_default sysfs_charger:file r_file_perms;
to the hal_health_default.te file.
Other than that, there are no other changes. So if you already downloaded the July 10 release and don't mind this small bug, you can wait until the August security patches before updating the rom. The August security patches and all future versions will have this bug fix incorporated.
New build called lineage-18.1-20210808-UNOFFICIAL-gt58wifi.zip
Aug 8 release notes
1. Fix battery status icon. When you plug in AC adapter, settings, battery does not show it charging even though it is. This is due to the sepolicy being too restrictive. I added https://github.com/retiredtab/msm89...mmit/c1eca9f7740b6a384d4fab8a1e8d812f59c17a99
2. Aug 5 security patches as per https://review.lineageos.org/c/LineageOS/android/+/314477
3. Whatever LiineageOS changed since last July release (about 11,500 files had to be recompiled).
4. 18.1 continues to be my daily driver since March 2021.
@retiredtab
Thanks for your work on this rom. It's been working very well.
It seems BiTGApps can no longer be downloaded.
ovalseven said:
It seems BiTGApps can no longer be downloaded.
Click to expand...
Click to collapse
Use opengapps then. Remember, this is not the correct place to ask gapps related questions. It's only for the rom. This will be the last time I mention gapps.
FAQ 13
Q13. I'm having problems with gapps, can you answer why it's not working?
A13. I will not answer any questions regarding gapps. This thread is about the rom, not gapps and I don't use gapps so I cannot help you. Android does not depend on gapps in order to work.
retiredtab said:
Q15. Can I turn off the on screen navigation keys?
Click to expand...
Click to collapse
Is there any way to swap the button positions to match the order of the hardware buttons (back button on the right)?
retiredtab said:
Use opengapps then. Remember, this is not the correct place to ask gapps related questions. It's only for the rom. This will be the last time I mention gapps.
FAQ 13
Q13. I'm having problems with gapps, can you answer why it's not working?
A13. I will not answer any questions regarding gapps. This thread is about the rom, not gapps and I don't use gapps so I cannot help you. Android does not depend on gapps in order to work.
Click to expand...
Click to collapse
I was just letting you know your links didn't work.
ovalseven said:
Is there any way to swap the button positions to match the order of the hardware buttons (back button on the right)?
I was just letting you know your links didn't work.
Click to expand...
Click to collapse
@ovalseven, the link in this thread's FAQ still works (for me, anyway) but the download link on that BiTGapps site appears not to be working. The BiTGapps thread [CUSTOM][GAPPS] BiTGApps for Android might have more information / an alternative download site.
ovalseven said:
Is there any way to swap the button positions to match the order of the hardware buttons (back button on the right)?
Click to expand...
Click to collapse
Now added to FAQ.
If you want to invert the onscreen keys, goto settings, system, buttons and enable invert layout
Thanks for the info and for your work on this rom. Been using it all afternoon and it's running smoothly.
lpedia said:
@ovalseven, the link in this thread's FAQ still works (for me, anyway) but the download link on that BiTGapps site appears not to be working. The BiTGapps thread [CUSTOM][GAPPS] BiTGApps for Android might have more information / an alternative download site.
Click to expand...
Click to collapse
Thanks to @lpedia letting me know, but it seems the developer of bitgapps has removed his links because of some "disagreement" with some users. I'm not involved in this and don't want to be, but if people want bitgapps, they should check the link daily to see when/if the developer will re-enable his links.
So I have now removed all gapps links from my FAQ and it's up to the user now to use their favourite search engine to find whatever gapps or Aurora Store they want. And THIS will be the FINAL word I say on gapps again.
New build called lineage-18.1-20210910-UNOFFICIAL-gt58wifi.zip
NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.
18.1 continues to be my daily driver since March 2021.
Sept 10 release notes
1. Reverted the patch to https://github.com/retiredtab/andro...mmit/a32c7a0bed536281d20b7c1cf8d41c84a268cc80
Removing systemUI from pinner services causes a 4 to 6 delay in bringing up the home screen. This is seen when loading or playing a game for about 20 minutes and then either hitting the recents or home button. By reverting this commit, pressing recents or home button brings up the systemUI right away.
2. Sept 5 security patches as per https://review.lineageos.org/c/LineageOS/android/+/315661
3. Whatever LiineageOS changed since last August release (about 6,200 files had to be recompiled).
This rom runs fantastic to anyone wondering. Easily the best running rom for t350 (i've tried them all). Thank you for your work on this.
Wikdclown said:
This rom runs fantastic to anyone wondering. Easily the best running rom for t350 (i've tried them all). Thank you for your work on this.
Click to expand...
Click to collapse
I totally agree with you! I just installed the Sept. 10th version on the 10th and it has made my tablet usable again. I will be sticking with this ROM from now on!
The ROM works very well, thank you @retiredtab !
All essential functionality works without caveats. Experimented with enabling pip and split screen and went back to this rom's default setting of being a "low memory" device, as it runs *much* smoother. Good choice of rom's default.
I ran into a couple of crashes in non-essential areas (setting a certain wallpaper crashed the settings, but then worked after reboot; turning on the hotspot then turning it off crashed settings, yet that was a pure curiosity, since there is no utility in the hotspot).
Have a question, pls. How to enable "Phone Ringtone" selection on the "Sound" page in Settings? Something in build.prop? [I use google voice as the voip app on other wifi-only tabs with same lineage version, works well, ringtone selection is there, just need to enable it in the rom for this t350 tab somehow].
Yxo 6o6uka said:
Have a question, pls. How to enable "Phone Ringtone" selection on the "Sound" page in Settings? Something in build.prop? [I use google voice as the voip app on other wifi-only tabs with same lineage version, works well, ringtone selection is there, just need to enable it in the rom for this t350 tab somehow].
Click to expand...
Click to collapse
Which wifi-only tabs give you that ringtone selection? I checked all my wifi 18.1 tablets msm8916 family, exynos 5420 and 5433 and none of them show the phone ringtone selection.
Samsung Tab Pro 8.4 SM-T320. Rom by Valera1978.