I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
I'm using nano/pico gapps.
Instructions
1. Install custom recovery
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
Work
Almost all
Known Issues
If you have wifi issues with latest release, please after install firmware apply patch:
SM-T320: https://drive.google.com/file/d/1E79Gcn7rNox2vP3OUd5FcVm2-a0aE12n/view?usp=sharing
SM-T325: https://drive.google.com/file/d/1fn1zJLL8dTJJJyoMEqph3DPH50YJp_gO/view?usp=sharing
Links
SM-T320
7. 20200411: march security patch, kernel update: https://drive.google.com/file/d/1I3QGfAEo55MKoEpBHBoZwj9a6EWzFBzA/view?usp=sharing
6. 20191211: december security patch, video recording, kernel from q with new wlan driver: https://drive.google.com/file/d/1YsniqI2RPwPKN9dB_7fKBAo9QkzxSFs_/view?usp=sharing
5. 20191130: latest sources, update kernel (autobrightness, some cleanup): https://drive.google.com/file/d/1swloB3vCfNsVzr9qsCmgpP8FpdrbXaJ2/view?usp=sharing
4. 20191112: november security patch: https://drive.google.com/file/d/1KQUcfna2rbeq8TLZfu44e63la59-rmzY/view?usp=sharing
3. 20191102: https://drive.google.com/file/d/1qJstVdMuPOM5ihsWqNvQeO4NyzsaVVIF/view?usp=sharing
2. 20191029: rollback dtb blocks to old stock: https://drive.google.com/file/d/1bY-vCQj57Gfgco1HeGbkkyjJEdOYOG2D/view?usp=sharing
1. 20191026: initial build: https://drive.google.com/file/d/1H3X036Qe9MJwEkE2zMPH5gQ05DLTkCzc/view?usp=sharing
SM-T325
4. 20200411: march security patch, kernel update: https://drive.google.com/file/d/13W9kC8RXK9CkqhDt5X9SQ7k9GISHbI5w/view?usp=sharing
3. 20191214: fix audio issues from last release: https://drive.google.com/file/d/1Mo3tPRTXtik2kBVNLJ8kw_bA6NJAgMuW/view?usp=sharing
2. 20191211: december security patch, ril + mobile data, internal speaker, kernel from q with new wlan driver: https://drive.google.com/file/d/13ARo1qiUh9MrNh9DHNlwxdo028cGpAjI/view?usp=sharing
1. 20191130: latest sources, update kernel (autobrightness, some cleanup), november security patch: https://drive.google.com/file/d/1Y4w1enXmMmDmLCvgzQSf5V6w-6wiPqLA/view?usp=sharing
Gapps
https://opengapps.org
Recovery
Use official version from:
SM-T320: https://twrp.me/samsung/samsunggalaxytabpro8.4wifi.html
SM-T325: https://twrp.me/samsung/samsunggalaxytabpro8.4lte.html
Sources
Sources: https://github.com/Lineageos
Device: https://github.com/Valera1978/android_device_samsung_mondrianwifi and https://github.com/Valera1978/android_device_samsung_mondrianlte
Kernel: https://github.com/Valera1978/android_kernel_samsung_msm8974
Vendor: https://github.com/Valera1978/android_vendor_samsung_mondrianwifi and https://github.com/Valera1978/android_vendor_samsung_mondrianlte
Thanks
Thanks to LineageOS team
Hello. 2 weeks ago with a big discount, I bought used a tab pro 8.4 wifi tablet.
I develop firmware for several tablets - note 12.2 on the same qcom 800, tab a 2016 on exynos 7870 (wifi<e) and a tab s3 on qcom 820 (wifi<e).
Initially, I thought, since the note pro is almost then same, as the tab pro series (actually, the note pro was develop based on the tab pro series), it turned out that these are huge differences, and I spent a huge amount of time to launch the tablet.
There were literally problems with everything - I spent almost a week launching just a panel and correctly turning it on/off. Then a huge amount of time to launch wifi and bt. Well, at the end, the sensors and cleanup the sources.
A bit later I'll build sm-t325 version and may be 10.1 sm-t525 (but I don't have this tablets, please send me to pm if you ready to help with test)
All my tablets already has android q. Of course after cleanups sm-t320 will get android q too.
Working for me only with pico gapps
del
Valera1978 said:
Hello. 2 weeks ago with a big discount, I bought used a tab pro 8.4 wifi tablet.
I develop firmware for several tablets - note 12.2 on the same qcom 800, tab a 2016 on exynos 7870 (wifi<e) and a tab s3 on qcom 820 (wifi<e).
Initially, I thought, since the note pro is almost then same, as the tab pro series (actually, the note pro was develop based on the tab pro series), it turned out that these are huge differences, and I spent a huge amount of time to launch the tablet.
There were literally problems with everything - I spent almost a week launching just a panel and correctly turning it on/off. Then a huge amount of time to launch wifi and bt. Well, at the end, the sensors and cleanup the sources.
A bit later I'll build sm-t325 version and may be 10.1 sm-t525 (but I don't have this tablets, please send me to pm if you ready to help with test)
All my tablets already has android q. Of course after cleanups sm-t320 will get android q too.
Click to expand...
Click to collapse
everything seems to work. thank you for this huge job
Thanks a lot! For me it works too!!! I used TWRP 3.2.3.0 and gapps mini (arm)! Dont forget a full wipe after installation.
Sent from my [device_name] using XDA-Developers Legacy app
@Valera1978
THX, you have done a great job, alot of us have waiting for this Version 16, camera works fine.
@Valera1978
Which Security Date has got this ROM.
Wound you like to update this ROM monthly with newest Patch level ?
bierma32 said:
@Valera1978
Which Security Date has got this ROM.
Wound you like to update this ROM monthly with newest Patch level ?
Click to expand...
Click to collapse
Current security update is october 2019.
You can monitor new update in: https://github.com/LineageOS/android_build/blob/lineage-16.0/core/version_defaults.mk , PLATFORM_SECURITY_PATCH define
Usually a new update appears on the 5-10th of the month (in lineage code) and after it I'm building new version.
Thank you for your working. I really expect the version of SM-T325
And what about SM-T520?
TechDriver said:
And what about SM-T520?
Click to expand...
Click to collapse
sm-t520 has differ platform. this is exynos5420 like t900\p900\901.
Thanks much! You brought a new life into my favorite tablet! It's hard to find a premium 8.4 tablet these days and hardware in this 5 year old one is running strong with your ROM.
Спасибо Валера!
Incredible to find developers still going strong in creating latest android version builds for this tablet after 5 years. Kudos to OP!
Works flawless and surely has added couple of more years life to the tablet now.
new versions.
Added version for sm-t325.
Unfortunately I do not have a t325 and I need somebody to test firmware. Please make backup efs/modem/may be all before test just in case.
Links in first post.
Valera1978 said:
new versions.
Added version for sm-t325.
Unfortunately I do not have a t325 and I need somebody to test firmware. Please make backup efs/modem/may be all before test just in case.
Links in first post.
Click to expand...
Click to collapse
I've tried test version on my SM-T325. There was repetitive rebooting problem initially and I cannot set anymore
However, thank you for your effort and I believe you can fix this problem.
How do i install this?
sorry to be a noob but this is my first time rooting an android device in about 8 years.
I have rooted by T320 and have super user.
I have installed the TWRP app.
I have odin.
I have all the downloads suggested on both my PC and my Samsung SD card.
WTF am i supposed to do from there? Do i install the mondrianwifi i find in the TWRP app if, so to boot or recovery? Or am i supposed to install the version the author linked. I hav read multiple articles but they don't explain what i am doing, why, how i should choose my options and they are all seriously out of date (given the age of the tablet)
Help!? Can someone give me a breadcrumb trail?
---------- Post added at 03:13 PM ---------- Previous post was at 02:51 PM ----------
scyto said:
sorry to be a noob but this is my first time rooting an android device in about 8 years.
Help!? Can someone give me a breadcrumb trail?
Click to expand...
Click to collapse
Ok i figured it out by a lot of poke and hope and got lucky.
I have the new firmware on with micro apps.
Was non intuitive how long the tablet takes after first reboot to get everything ready and WTF is that slider / circle animation - i thought it was telling me to slide my finger from right to left (that was up for like 2.5 mins the first time) luckily i just waited.
On first use lots of apps reported crashing most stopped but BT app was in infinite reboot.
Did hard reboot and the BT app is still infinitely rebooting along with android.process.media
Trying a factory reset, use TWRP to wipe device (all but SD card) and reinstall to fix....
---------- Post added at 03:32 PM ---------- Previous post was at 03:13 PM ----------
now its hung at the strange animation for more than 10 mins and power button does nothing? What next?
Another wipe and re-install not connected to USB seemed to fix it.
nrpia said:
I've tried test version on my SM-T325. There was repetitive rebooting problem initially and I cannot set anymore
However, thank you for your effort and I believe you can fix this problem.
Click to expand...
Click to collapse
Please post logs,
SM-T325 builds appreciated
Valera1978 said:
new versions.
Added version for sm-t325.
Unfortunately I do not have a t325 and I need somebody to test firmware. Please make backup efs/modem/may be all before test just in case.
Links in first post.
Click to expand...
Click to collapse
WOW just WOW
@Valera1978 Thank you for all your efforts and bringing this device back to life! I'm happily looking forward to test builds for the SM-T325 and provide logs if needed.
Valera, What is new in release from 11/02 (lineage-16.0-20191102-UNOFFICIAL-mondrianwifi)? Or it is targeted to owners of SM-T325 and you just misplaced it in SM-T320 section?
Related
Sailfish OS for the HTC Desire HD
Announcing Sailfish for the HTC Desire HD
What is Sailfish?
http://en.wikipedia.org/wiki/Sailfish_OS
This is not Android!
This should be thought of as a development experiment. It may be useful if you are a developer and want to write/port apps the the Sailfish operating system. It is not an end-user product, however, if you wish to experiment and try something different then feel free!
Please do not contact Jolla Care or Jolla Developer Care, as this is not the Jolla phone
Video
Special Thanks
To Mustaavalkosta for the CM11 kernel and answering my queries via Google Hangouts!
The sailfishos porters in #sailfishos-porters on freenode
Installation
Make sure you have an up-to-date recovery. I used 4ext touch. Philz recovery doesnt have the required tar command.
Format/wipe etc
For version < pgz11 Install the latest CM10.1 and make sure it works
For pgz11 onwards Install CM 12.1 nightly 20120131 from http://forum.xda-developers.com/htc-desire-hd/development/rom-cyanogenmod-12-1-nightlies-t3070621
Copy the .zip to the SDCard and install it. The installation script take a little time.
First Run
On first run you are presented with a language selection, after this time you should be presented with the first-run wizard. Complete as much as possible, but dont try and create a Jolla account as there wont be a network connection (unless you have inserted a sim and by chance it works, I havnt tested that). To get out of the wizard, scroll down because the 'skip' link is off the bottom of the screen.
Hardware Status
https://wiki.merproject.org/wiki/Adaptations/libhybris
Bugs
Lots
Several major graphical bugs, such as the keyboard struggling to show and corruption in the windows of minimized apps. This is probably down the the kernel hack I made to get apps to load. (no longer true as of pgz11)
Cellular network is pretty unusable. No audio input! (fixed in pgz13)
Proximity sensor is not working and blanks the screen (note, progress has been made on this)
Mobile data is not working (being worked on) (fixed in pgz13)
Notes
Downloads
Version pgz1
Version pgz2
Version pgz3
Version pgz4
Version pgz5
Version pgz11
Version pgz12
Version pgz13
History
pgz1:
Initial Version
pgz2 (11-Oct-2014):
Fixed sound (output only, see notes)
Fixed developer options in settings
Added some extra programs (including the open source app store and my own game
First boot works without restart
pgz3 (22-Oct-2014)
Connects to Cellular network (see bugs)
Fixed usb-networking in the release build
Tweaked boot to remove root access/debug mode
pgz4 (28-Oct-2014)
Based on the new Sailfish 1.1.0.39
Fixed some init bugs
pgz5 (11-Jan-2015)
Based on new Sailfish 1.1.1.27
Disabled Proximity Sensor until MCE is fixed
pgz11 (4-Feb-2016)
Based on Sailfish 2.0.1.7 and CM12.1
New video drivers
Better all-round
pgz12 (7-Fen-2016)
Fixed sensors
Fixes sound
Updated ofono but no mobile network yet
pgz13 (14-Feb-2016)
Calls work
Mobile data works
Reliability not guaranteed!
XDA:DevDB Information
Sailfish, ROM for the HTC Desire HD
Contributors
PiggZ, piggz
ROM Kernel: Linux 3.0.x
Based On: Cyanogenmod
Version Information
Status: Alpha
Created 2014-09-19
Last Updated 2014-09-19
Interesting, this is great.
I suggest you post in the right thread for people to see this amazing project you have started.
Sailfish for our device; keep up the good work, will love to see more.
hope it doesn't end here.
That's a great rom, especially if it can work for daily driver. Using the DHD with sailfish and respond as fast as a dual or quad android phone would be great(even if it's not android)
1st I prefer speed/response time
2nd then android (I prefer 1st anyday)
This actually seems pretty cool! The feel I get is that this is miles ahead of Ubuntu Touch when I was working on it. It would be fun to see how awesome this could get with a full development team working on it as their dayjob. After all, this seems to be more suitable for old single-core device than the latest Android versions have been. Great job PiggZ! :good:
Sound is working
Good news peeps, I got sound output working! A new rom will follow in a few days
Ive been using this for the last weeks to allo developing sailfish applications, and for that purpose it is working just fine. Ive not attempted to get the mobile network up yet, but i'll make some enquiries.
Obviously development so moved to the right place.
OP, please make sure you have the ability to post in this thread. If not, please let me know.
Good luck!
brilliant work
coal686 said:
Obviously development so moved to the right place.
OP, please make sure you have the ability to post in this thread. If not, please let me know.
Good luck!
Click to expand...
Click to collapse
Nice work!!
I gotta try this!
Thrad location
Ive asked for the thread to be moved into the Andoid Developent sub section, I hope you think thats ok
Hardware Table
It's in early phase of development.
First, take a look at the hardware table.
Version pgz2 available
Just uploaded a new version.
See post #1 for details ... its still uploading so give it 30 minutes or so!
PiggZ said:
Just uploaded a new version.
See post #1 for details ... its still uploading so give it 30 minutes or so!
Click to expand...
Click to collapse
Whats working in the new build?
Where is the changelog?
it says in post 1 under History
Update
Just a small update, I managed to make a call from Sailfish on the ACE!
It wasnt a great experience...the proximity sensor is playing up, so I want that working before I make any update.
Adam
Maybe, this is the last big interesting thing in this legacy device...:laugh:
PiggZ said:
Just a small update, I managed to make a call from Sailfish on the ACE!
It wasnt a great experience...the proximity sensor is playing up, so I want that working before I make any update.
Adam
Click to expand...
Click to collapse
Awesome man , didn't expect to see sailfish here and yet you made it possible , cheers.
New release (pgz3)
Pgz3 is released.
See post 1 for download. Highlights include a somewhat not really working cellular connection and improved boot and developer tools.
sorry
PiggZ said:
Pgz3 is released.
See post 1 for download. Highlights include a somewhat not really working cellular connection and improved boot and developer tools.
Click to expand...
Click to collapse
I don't know why,while none of the versions can boot?
admet615 said:
I don't know why,while none of the versions can boot?
Click to expand...
Click to collapse
Sure they do, or I wouldnt release them
Have you done
wipe data
install cm 10.1 stable
install sailfish
?
PiggZ said:
Sure they do, or I wouldnt release them
Have you done
wipe data
install cm 10.1 stable
install sailfish
?
Click to expand...
Click to collapse
I'm sure,I have wiped data,cache and all the data except the SD,then installed the Sailfish,I used the CM11.
CyanogenMod is a free, community built distribution of Android 5.1 (Lollipop) which greatly extends the capabilities of your phone.
Here is unofficials builds of CyanogenMod 12.1 for HTC One Mini (m4).
How to get this ?
You need the last .zip package (15/12/11) : https://www.damien-boyer.com/downloads.html
And the 5.1 gapps : https://www.androidfilehost.com/?fid=95916177934550851
Progress of the Project:
26 Dec 2014: Initial Release
19 Jan 2015: Fix Camera and lot of other things.
27 Jan 2015: Sources updated. New CM bootanimation.
06 Apr 2015: CyanogenMod 12.1 - Android-5.1.0_r3
15 Apr 2015: Updated.
08 Jun 2015: Updated by @Wingman2K
11 Jun 2015: Updated by @Wingman2K
15 Jun 2015: Updated by @Wingman2K
21 Jun 2015: Updated by @Wingman2K. Check the changelog.
27 Jun 2015: Re-sync + CM12.1's MSM8960
16 Jul 2015: Re-sync + TeamEOS kernel source
13 Oct 2015: Re-sync by @Wingman2K.
11 Dec 2015: Last CM12.1 Build
Issues
Memory leaks and other lags.
How can I install it ?
1. Copy the ROM and the Gapps in your device
2. Reboot in recovery (TWRP or CWM)
3. Wipe
4. Flash the ROM
5. Flash the Gapps
6. Reboot
7. Enjoy the ROM
Don't forget to contribute
Donate with Paypal
XDA DevDB Information
CyanogenMod 12.1 for HTC One Mini - m4, ROM for the HTC One Mini.
Source Code: https://github.com/CyanogenMod/android/tree/cm-12.1
Kernel Source: github.com/TeamEOS
Blobs: https://github.com/TheMuppets
ROM OS Version: 5.1.1 Lollipop
ROM Kernel: Linux 3.4.x
Version Information
Status: Beta
Created 2014-12-26
Last Update 2015-12-11
Special thanks to @mattplo & @Wingman2K
first
another LP rom for our beloved M4 , nice i'll try this right now
Trying to patch in D2W/S2W for the kernel from CM11 patch. Its fighting me.
After a day of use, the rom run flawlessly apart somes lag on intensive use, i have got redraw and 2 cases of reboot ... I will try to reproduce that and bring catlog ... However the rom is very stable for first release, keep up the good work
Sent from my One Mini using XDA Free mobile app
Thanks for you report @malikou
Very Good Rom
This Rom is realy great and fast, I'm not a heavy user of my mini but I didn't have an issue since yesterday only Camera - do you have a fix already? Thanks.
@dvb127 : Thanks for your report. I have others projects so no fixes for the moment
The proximity sensor dont work ... Apart this i didnt got redraw or reboot since 2 days, every think seems to be good i ll continue reporting if i found another issues ...
Sent from my One Mini using XDA Free mobile app
malikou said:
The proximity sensor dont work ... Apart this i didnt got redraw or reboot since 2 days, every think seems to be good i ll continue reporting if i found another issues ...
Sent from my One Mini using XDA Free mobile app
Click to expand...
Click to collapse
I actually have this fixed but at the cost of a major crash that leads to a reboot after the screen attempt to come back on when a call has ended. As soon as I get back to the mainland (I'm on vacation in the Caribbean) where bandwidth is plentiful I'll get in contact with the OP if he has time.
Sorry for this, but since the CM11 and the sudden death of One Mini's issue, I'm concerned.
Has it been solved ?
Is CM12 having similar issues, or not ?
I've lost quite a few episodes, so I don't know if it been fixed since CM11 latest updates, etc.
htc_one_mini_m4 said:
Sorry for this, but since the CM11 and the sudden death of One Mini's issue, I'm concerned.
Has it been solved ?
Is CM12 having similar issues, or not ?
I've lost quite a few episodes, so I don't know if it been fixed since CM11 latest updates, etc.
Click to expand...
Click to collapse
There has been no official statement on this issue.
An updated thermald config was implemented in CM-code somewhere last summer/fall, presumably solving the overheating issue.
It is not 100% clear whether issue is solved, though, because there has been at least 1 report of overheated & bricked M4 under the patched thermald config right after it was first posted as a separate patch.
I must say the above applies only to the official CM11 M7 snapshop and nightlies thereafter. I have no experience or knowledge about later snapshots or this, unofficial CM12 port.
Can only say there have been no reports on XDA about bricked devices somehwere since summer/fall.
pure.by said:
There has been no official statement on this issue.
An updated thermald config was implemented in CM-code somewhere last summer/fall, presumably solving the overheating issue.
It is not 100% clear whether issue is solved, though, because there has been at least 1 report of overheated & bricked M4 under the patched thermald config right after it was first posted as a separate patch.
I must say the above applies only to the official CM11 M7 snapshop and nightlies thereafter. I have no experience or knowledge about later snapshots or this, unofficial CM12 port.
Can only say there have been no reports on XDA about bricked devices somehwere since summer/fall.
Click to expand...
Click to collapse
Thank you very much mate!
You're always around helping people
New build out.
Check first page, new build fix camera and a lot of others things.
AndroGeek974 said:
New build out.
Check first page, new build fix camera and a lot of others things.
Click to expand...
Click to collapse
Nice job! Like the CM12 Themer...although there are some issues with lockscreen wallpaper, I understand that is across the board.
Has the bluetooth audio problem that I'm experiencing in the Candy Rom as well. Currently using your rom as my daily driver because that's really all the issues I'm having.
Very peppy and happy to see another version of Lollipop for our device!
Thanks for your report man !
I think these types of issues gonna be fix in future builds, in fact it depends of the blobs and cm updates.
I'll try to make weekly builds of this ROM.
AndroGeek974 said:
Thanks for your report man !
I think these types of issues gonna be fix in future builds, in fact it depends of the blobs and cm updates.
I'll try to make weekly builds of this ROM.
Click to expand...
Click to collapse
Thanks for a great ROM dude I am also using as my daily driver, got same issue with Bluetooth Audio and seem to have slight connectivity issues nothing major (might not be ROM related) but is first time have experienced this. Looking forward to your future builds.
27/01 build
Update: Finally got around to flashing this. Glad to say everything works as expected. However, I didn't test its Bluetooth. It comes on just not sure how solid it is. But aside from that. Great build.
All of the new features CM guys incorporated are pretty snazzy too.
Waiting for my SO to get home and I'll flash this.
hi/mic issue
flashed this rom.
everything is working finde. BUT still there is for me an issue with the microphone. i had it on cm11 too
during calls, the other one cant hear me good, i think the mic volume is too low. is there a way to boost it?
PS: On my S1 Galaxy there is a app called "voodoo sound". with this app i could boost mic volume and the other one could hear me better.
But after long searches i couldnt find similar apps for the one mini.
With the insert coin rom the problem is still there, but i think with cm its worse. i need this mic fix, otherwise i cant use this phone any longer -.-
official CM release?
Hi,
is a official cyanogenmod 12 release planed for M4?
thx
This is another adaptation of @ottmi's work, this time to AICP (64bit). It started as an experiment by request of @josoft86, tested on an italian forum, but it turned out to be rather appreciated.
Credits go to the usual list of suspects: @ottmi (obviously!), @dev_harsh1998 (device tree), @lolmaxlik_ru (peach device tree).
Due to the build system, in order for russian friends to use the ROM on their Ark Benefit A3s, I had to make a separate build for them; I used the @lolmaxlik_ru device tree with some changes for 64bit:
https://github.com/siljaer/device_ark_peach
The kernel is based on Lineage kernel, with code for the Trunk from @ottmi's kernel. Kernel source is here:
https://github.com/siljaer/android_kernel_qcom_msm8916
Link for Trunk build: https://www.androidfilehost.com/?fid=673956719939816002
Link for Peach build: https://www.androidfilehost.com/?fid=745849072291695487
You are welcome to report any problem!
XDA:DevDB Information
AICP 12.1 for trunk/peach, ROM for the Android General
Contributors
siljaer, ottmi, @dev_harsh1998, @lolmaxlik_ru
Source Code: https://github.com/siljaer/android_device_elephone_trunk/tree/n7.1
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: AICP
Version Information
Status: Snapshot
Created 2017-12-14
Last Updated 2018-01-30
Reserved
Reserved
Changelog
20171217/20171218: kernel update (latest CAF and kernel 3.10.108 merge), December android updates
20171212: initial release
thanks!
can I use dirty upgrade from last ottmi's build ?
is mediaserver works as expected in your roms ?
karabassssss said:
thanks!
can I use dirty upgrade from last ottmi's build ?
is mediaserver works as expected in your roms ?
Click to expand...
Click to collapse
Sorry, I guess dirty upgrade is not possible. Camera and video recording are working AFAIK. I am not using this ROM as a daily driver, but people who are report so.
installed 20171217 version on trunk.
so far all works including mediaserver!
Thanks a lot!
karabassssss said:
installed 20171217 version on trunk.
so far all works including mediaserver!
Thanks a lot!
Click to expand...
Click to collapse
Thanks for your feedback!
will you keep it up in the near future or this is occasional build ?
karabassssss said:
will you keep it up in the near future or this is occasional build ?
Click to expand...
Click to collapse
Actually, I am not using it; as I told, this ROM was born because of a kind request by @josoft86. It was just an experiment, but it turned out that AICP (after they transitioned from oracle java to openjdk) was quite simple to build.
However, if some people are using it and ask for it, I can rebuild it in order to include monthly changes. If people report problems, I can try and solve them. It's up to you, basically
In the past I had problems with disk space, now I have plenty of space on an external drive and I have also set up a partition for building ROMS (no more virtual machines...), so it's not a big deal.
siljaer said:
Actually, I am not using it; as I told, this ROM was born because of a kind request by @josoft86. It was just an experiment, but it turned out that AICP (after they transitioned from oracle java to openjdk) was quite simple to build.
However, if some people are using it and ask for it, I can rebuild it in order to include monthly changes. If people report problems, I can try and solve them. It's up to you, basically
In the past I had problems with disk space, now I have plenty of space on an external drive and I have also set up a partition for building ROMS (no more virtual machines...), so it's not a big deal.
Click to expand...
Click to collapse
I'll be more than happy! thanks!!
karabassssss said:
I'll be more than happy! thanks!!
Click to expand...
Click to collapse
Fine. I've just made a new build, but it has still December security updates (but a new boot animation ).
I will try again in a few days, in order to publish something with more significant changes
fantastic, thanks
One thing,
not sure it related to aicp build, but it started to happen only when moved from ottmi's last build to aicp.
Sometimes , when phone goes into sleep mode, it unable to wake up no matter what you doing. Only removing battery and reinserting it back solves the problem.
Thanks
karabassssss said:
One thing,
not sure it related to aicp build, but it started to happen only when moved from ottmi's last build to aicp.
Sometimes , when phone goes into sleep mode, it unable to wake up no matter what you doing. Only removing battery and reinserting it back solves the problem.
Thanks
Click to expand...
Click to collapse
Thanks for your feedback, I will try to investigate. Meanwhile, I tried to compile AICP but it did not show Jan updates. I will make another build soon, no matter if it is updated, so you will be able to try it and see whether the problem still occurs.
great! thanks in advance
karabassssss said:
great! thanks in advance
Click to expand...
Click to collapse
New build is ready. Actually, I think AICP development for 12.1 has stalled, due to 13.1 progress. So, this is likely the last build for a while. As soon as an official build pops up for a msm8916 device I will try porting that. Let me know whether the problem you reported persists.
thanks. will try & report
just_person said:
Hey.
The display of the smartphone does not work after installing the firmware. I have Ark Benefit A3, but the motherboard from Elephone Trunk. I tried to install aicp_peach_n-12.1-UNOFFICIAL-20171218 and aicp_trunk_n-12.1-UNOFFICIAL-20180130
Previously used the firmware aicp_peach_n-12.1-NIGHTLY-20170709. (Sorry for my English, translate.google)
Click to expand...
Click to collapse
I assume you have a Trunk with an A3 screen; am I right?
Thanks for the feedback. Would you please give me more details about the problem?
Can you revert to the previously working firmware?
https://github.com/LineageOS/android_device_huawei_msm8916-common/tree/lineage-15.0
this isn't suitable ?
karabassssss said:
https://github.com/LineageOS/android_device_huawei_msm8916-common/tree/lineage-15.0
this isn't suitable ?
Click to expand...
Click to collapse
Kernel isn't a problem: I got major help by @dev_harsh1998 to patch trunk's kernel. So far, my tries to build anything Oreo for the trunk have failed. I am going to try again, but not in a short time (I am quite busy at the moment).
With HD10 (2017) unlock/TWRP available - link (thanks to @k4y0z!!!), the next natural question is a custom ROM. The subject may turn out to be slightly trickier than what appears at first sight.
Let's have a discussion thread to brainstorm on this and not wonder off-topic in other places.
I had seen @DragonFire1024 & @Rortiz2 tried to work on that, so feel free to chime in as necessary.
What we have:
HD10 (2017) chipset - MT8173 (2+2 cores), there is an beefier brother to it, MT8176 (2+4 cores). For most practical purposes both chipsets seem almost identical software-wise.
MT8173 was introduced in March 2015 (time of Lollipop domination - Android 5). MT8176 was introduced in October 2016 (getting toward Nougat - Android 7).
The efforts up to date on a custom ROM for this chipset appear to be by @Goayandi, who is still active on XDA, so his work could be used a starting point. I believe @Goayandi was working on Android 7 (Nougat). Here are some of the original links:
XDA : Mediatek MT8173 & MT8176 development
Reddit: Mediatek MT8173 & MT8176 development
Stuff from Amazon for MT8173 (both HD10 2017 and FireTV2) is Lollipop-vintage (Android 5), other devices with these chipsets seem to have reached Nougat (Android 7). It does not appear that there is any known MT8173/MT8176 device with Android 8, or 9 (or is there?). It seems that @diplomatic has an Asus like this with Nougat.
At the moment, it feels a a Nougat custom ROM might be the ceiling for the device, given the difficulties of finding proprietary pieces for MTK chipsets to get Android 8 or 9 going. Now, even Android 7 is still a bit of a challenge, given limited prior success.
More thoughts/ideas? Feel free to fill this thread with random thoughts as much as you want - that's what it's for!!!
I'm really looking forward to an AOSP experience on this tablet, to be honest. Can't wait to see what they come up with!
GuyInDogSuit said:
I'm really looking forward to an AOSP experience on this tablet, to be honest. Can't wait to see what they come up with!
Click to expand...
Click to collapse
As long as I can set up everything properly I'm ready to go. I've managed to get past script issues I think. I can get it to flash and it boots to the orange fire logo and sits for eternity. This was the same result pre and post TWRP. So at this point it's probably the installation and improper setup of the tree and files. If someone can point me to a guide or give me instructions on how to add support to my AOSP working directory, that would be great. This bit of the leg work is hard as there really aren't any guides that are detailed enough or that work anymore.
Secondly, I think if we are going to use a kernel, we either use the 7.0 source, or just use the kit I have to build our own. Amazon cherry picked the crap out of the kernel practically to the bare bones, so I think expanding from it is just a waste of time, especially since we have the kit that does a lot of the work for us, including providing signatures and the tools to sign etc.
Sent from my Galaxy Tab3 Lite 7.0 using XDA Labs
I wouldn't mind even if the best ROM available is a 6.0 Marshmallow one. Anything that gives AOSP on a stable base for the Fire HD10 is going to be awesome.
DragonFire1024 said:
As long as I can set up everything properly I'm ready to go. I've managed to get past script issues I think. I can get it to flash and it boots to the orange fire logo and sits for eternity. This was the same result pre and post TWRP. So at this point it's probably the installation and improper setup of the tree and files. If someone can point me to a guide or give me instructions on how to add support to my AOSP working directory, that would be great. This bit of the leg work is hard as there really aren't any guides that are detailed enough or that work anymore.
Secondly, I think if we are going to use a kernel, we either use the 7.0 source, or just use the kit I have to build our own. Amazon cherry picked the crap out of the kernel practically to the bare bones, so I think expanding from it is just a waste of time, especially since we have the kit that does a lot of the work for us, including providing signatures and the tools to sign etc.
Sent from my Galaxy Tab3 Lite 7.0 using XDA Labs
Click to expand...
Click to collapse
So did you end up successfully unbricking your device?
I did share working amazon kernel sources in the HD-10 Unlock thread.
They worked well in my tree to compile TWRP.
k4y0z said:
So did you end up successfully unbricking your device?
I did share working amazon kernel sources in the HD-10 Unlock thread.
They worked well in my tree to compile TWRP.
Click to expand...
Click to collapse
Sorry for being out of the loop - were those kernel sources for Lollipop? Or does it even matter at all - meaning they would be good to go with newer Android versions as well.
Could you link to those posts in here?
bibikalka said:
Sorry for being out of the loop - were those kernel sources for Lollipop? Or does it even matter at all - meaning they would be good to go with newer Android versions as well.
Could you link to those posts in here?
Click to expand...
Click to collapse
They will likely need some patches to work with newer versions, but it's a good start I'd say.
It's the most recent version amazon has published.
k4y0z said:
So did you end up successfully unbricking your device?
I did share working amazon kernel sources in the HD-10 Unlock thread.
They worked well in my tree to compile TWRP.
Click to expand...
Click to collapse
I am working on it as we speak. I downloaded the zip from the second post in this thread, 1.1. extracted and ran sudo ./bootrom-step.sh. said it can't find build/payload directory it doesn't exist. So I assume I use that folder from the other unbricking thread copy it to yours? Assuming its a yes to that question, I keep getting the serial port errors. I also had to delete a setting in udev (this was my own addition to it) and rebooted PC. Now I am having a cigarette. When I do it again, if I still get serial port errors, time to try each of the 8 or 10 other ports on the PC.
Sent from my MotoG3 using XDA Labs
---------- Post added at 06:23 PM ---------- Previous post was at 06:21 PM ----------
bibikalka said:
Sorry for being out of the loop - were those kernel sources for Lollipop? Or does it even matter at all - meaning they would be good to go with newer Android versions as well.
Could you link to those posts in here?
Click to expand...
Click to collapse
The one I have and provided is a source to 7.0. looks nicely stocked.
Sent from my MotoG3 using XDA Labs
bibikalka said:
With HD10 (2017) unlock/TWRP available - link (thanks to @k4y0z!!!), the next natural question is a custom ROM. The subject may turn out to be slightly trickier than what appears at first sight.
Let's have a discussion thread to brainstorm on this and not wonder off-topic in other places.
I had seen @DragonFire1024 & @Rortiz2 tried to work on that, so feel free to chime in as necessary.
What we have:
HD10 (2017) chipset - MT8173 (2+2 cores), there is an beefier brother to it, MT8176 (2+4 cores). For most practical purposes both chipsets seem almost identical software-wise.
MT8173 was introduced in March 2015 (time of Lollipop domination - Android 5). MT8176 was introduced in October 2016 (getting toward Nougat - Android 7).
The efforts up to date on a custom ROM for this chipset appear to be by @Goayandi, who is still active on XDA, so his work could be used a starting point. I believe @Goayandi was working on Android 7 (Nougat). Here are some of the original links:
XDA : Mediatek MT8173 & MT8176 development
Reddit: Mediatek MT8173 & MT8176 development
Stuff from Amazon for MT8173 (both HD10 2017 and FireTV2) is Lollipop-vintage (Android 5), other devices with these chipsets seem to have reached Nougat (Android 7). It does not appear that there is any known MT8173/MT8176 device with Android 8, or 9 (or is there?). It seems that @diplomatic has an Asus like this with Nougat.
At the moment, it feels a a Nougat custom ROM might be the ceiling for the device, given the difficulties of finding proprietary pieces for MTK chipsets to get Android 8 or 9 going. Now, even Android 7 is still a bit of a challenge, given limited prior success.
More thoughts/ideas? Feel free to fill this thread with random thoughts as much as you want - that's what it's for!!!
Click to expand...
Click to collapse
Hi bibikalka,
Very good idea this thread.
What you can do, is to port a port a ROM of another MT8173 tablet to the FIRE HD10 2017.
This works and I have tested it on my BQ Aquaris M8 (MT8163) it has a similar MTK so I guess it will work. I have ported for example a ROM of an asus zenpad that uses MT8163 and at least the rom boots.
BTW: Oreo on MT8176: https://www.xda-developers.com/alldocube-x-10-5-inch-android-8-1-oreo/
DragonFire1024 said:
I am working on it as we speak. I downloaded the zip from the second post in this thread, 1.1. extracted and ran sudo ./bootrom-step.sh. said it can't find build/payload directory it doesn't exist. So I assume I use that folder from the other unbricking thread copy it to yours? Assuming its a yes to that question, I keep getting the serial port errors. I also had to delete a setting in udev (this was my own addition to it) and rebooted PC. Now I am having a cigarette. When I do it again, if I still get serial port errors, time to try each of the 8 or 10 other ports on the PC.
Click to expand...
Click to collapse
Apparently I forgot to add the right files.
give me a moment.
---------- Post added at 06:47 PM ---------- Previous post was at 06:36 PM ----------
DragonFire1024 said:
I am working on it as we speak. I downloaded the zip from the second post in this thread, 1.1. extracted and ran sudo ./bootrom-step.sh. said it can't find build/payload directory it doesn't exist. So I assume I use that folder from the other unbricking thread copy it to yours? Assuming its a yes to that question, I keep getting the serial port errors. I also had to delete a setting in udev (this was my own addition to it) and rebooted PC. Now I am having a cigarette. When I do it again, if I still get serial port errors, time to try each of the 8 or 10 other ports on the PC.
Click to expand...
Click to collapse
I have fixed the upload, please use amonet-suez-v1.1.1.zip
DragonFire1024 said:
The one I have and provided is a source to 7.0. looks nicely stocked.
Click to expand...
Click to collapse
But these aren't amazon sources are they?
They probably are missing some drivers then.
But if they are for mt8173 they could be used as a source to patch the amazon-sources.
k4y0z said:
Apparently I forgot to add the right files.
give me a moment.
---------- Post added at 06:47 PM ---------- Previous post was at 06:36 PM ----------
I have fixed the upload, please use amonet-suez-v1.1.1.zip
But these aren't amazon sources are they?
They probably are missing some drivers then.
But if they are for mt8173 they could be used as a source to patch the amazon-sources.
Click to expand...
Click to collapse
I'll provide a link in a few. Trying your fix now.
Sent from my Galaxy Tab3 Lite 7.0 using XDA Labs
Rortiz2 said:
Hi bibikalka,
Very good idea this thread.
What you can do, is to port a port a ROM of another MT8173 tablet to the FIRE HD10 2017.
This works and I have tested it on my BQ Aquaris M8 (MT8163) it has a similar MTK so I guess it will work. I have ported for example a ROM of an asus zenpad that uses MT8163 and at least the rom boots.
BTW: Oreo on MT8176: https://www.xda-developers.com/alldocube-x-10-5-inch-android-8-1-oreo/
Click to expand...
Click to collapse
Excellent find! Here is a review link:
https://forum.xda-developers.com/ge...ldocube-x-review-media-playback-king-t3902539
Alldocube X kind of has 2x of everything compared to HD10 2017, but at 2x price I wonder how fast Oreo would be on HD10 and if 2Gb of RAM would cut it. But this is definitely the device to copy if one wants latest and greatest!
And here is a thread with misc download links for ROMs:
https://forum.xda-developers.com/ge...n/10-5-inch-super-amoled-2560-x-1600-t3821327
bibikalka said:
Excellent find! Here is a review link:
https://forum.xda-developers.com/ge...ldocube-x-review-media-playback-king-t3902539
Alldocube X kind of has 2x of everything compared to HD10 2017, but at 2x price I wonder how fast Oreo would be on HD10 and if 2Gb of RAM would cut it. But this is definitely the device to copy if one wants latest and greatest!
And here is a thread with misc download links for ROMs:
https://forum.xda-developers.com/ge...n/10-5-inch-super-amoled-2560-x-1600-t3821327
Click to expand...
Click to collapse
I will try to port lineage 15.1 but the safest thing is that it will not work.
I have also ported an AOSP Rom for anyone who wants to try it. Tomorrow I will give more info.
Rortiz2 said:
I will try to port lineage 15.1 but the safest thing is that it will not work.
I have also ported an AOSP Rom for anyone who wants to try it. Tomorrow I will give more info.
Click to expand...
Click to collapse
This is great news! I am eagerly awaiting more info about this AOSP ROM
Rortiz2 said:
I will try to port lineage 15.1 but the safest thing is that it will not work.
I have also ported an AOSP Rom for anyone who wants to try it. Tomorrow I will give more info.
Click to expand...
Click to collapse
ffstudios said:
This is great news! I am eagerly awaiting more info about this AOSP ROM
Click to expand...
Click to collapse
Alright, we have both an eager developer, and a tester!!! Just remember, avoid bricking !
Very recently (March 2019) @wangyiling seems to have put together a LineageOS 15.1 ROM for MT8173/8176 - link, so hopefully we can re-purpose that for HD10. It's great to have an active developer elsewhere looking at the same thing!
It feels that if there is at least something that boots the kernel, it'd be a huge step forward.
bibikalka said:
Alright, we have both an eager developer, and a tester!!! Just remember, avoid bricking !
Very recently (March 2019) @wangyiling seems to have put together a LineageOS 15.1 ROM for MT8173/8176 - link, so hopefully we can re-purpose that for HD10. It's great to have an active developer elsewhere looking at the same thing!
It feels that if there is at least something that boots the kernel, it'd be a huge step forward.
Click to expand...
Click to collapse
If my testing on ROMs caused my brick, we have to be careful. I've been testing and flashing test ROMs for months now and never bricked like this. I think I may know what happened and if I'm right, I'm not sure what effect if any this will have on flashing a rom. According to the fstab.mt8173 file in the root directory, the partitions we flash for a rom, aren't part of the EMMC: data, system, cache are all ext4. All other partitions are however EMMC. So if I recall correctly, I did list the system as EMMC in the build script, but did intend to remove it. I made a last minute adjustment to the script and didn't change that part though.
https://forum.xda-developers.com/showpost.php?p=78542898&postcount=618
Sent from my MotoG3 using XDA Labs
Rortiz2 said:
I will try to port lineage 15.1 but the safest thing is that it will not work.
I have also ported an AOSP Rom for anyone who wants to try it. Tomorrow I will give more info.
Click to expand...
Click to collapse
I too am willing to test. Just let me know and I'll be sure to wear my best testing pants. [emoji41]
Sent from my SM-G9650/DS running stang5litre Pie ROM
AOSP ROM TEST 1 (suez)
Ok guys so here's the first test for the AOSP ROM.
First of all, I am not responsible for bricked devices. It is you who decides to try the ROM without knowing if it will work because it is a TEST.
DOWNLOAD: Removed
INSTALL INSTRUCTIONS:
- Boot TWRP
- Make NANDROID BACKUP
- Make wipes
- Format data
- Install ROM
- Reboot
Please. If the installation fails, send the errors and if the ROM starts, comment on the bugs.
Regards!
Rortiz2 said:
Ok guys so here's the first test for the AOSP ROM.
First of all, I am not responsible for bricked devices. It is you who decides to try the ROM without knowing if it will work because it is a TEST.
DOWNLOAD: https://mega.nz/#!C5dEQIKR!14BcGTiaT-xsrPUc-AxmWrTLj92Y5A2VgeNX2VA1uUE
INSTALL INSTRUCTIONS:
- Boot TWRP
- Make NANDROID BACKUP
- Make wipes
- Format data
- Install ROM
- Reboot
Please. If the installation fails, send the errors and if the ROM starts, comment on the bugs.
Regards!
Click to expand...
Click to collapse
Sounds good to me. Won't have a chance till later this afternoon/evening to give it a whirl, but when I do I'll definitely share my results and any information that may be useful. Thank you!
Sent from my SM-G9650/DS running stang5litre Pie ROM
Rortiz2 said:
Ok guys so here's the first test for the AOSP ROM.
First of all, I am not responsible for bricked devices. It is you who decides to try the ROM without knowing if it will work because it is a TEST.
DOWNLOAD: https://mega.nz/#!C5dEQIKR!14BcGTiaT-xsrPUc-AxmWrTLj92Y5A2VgeNX2VA1uUE
...
Please. If the installation fails, send the errors and if the ROM starts, comment on the bugs.
Click to expand...
Click to collapse
Which AOSP version is this? Could you try that Oreo Lineage stuff from @wangyiling at some point as well?
One of these days we'll have a ROM developer and a tester within the same person Too bad we've lost @DragonFire1024 since his tablet got bricked
This is the official build of Jaguar Rom. I have been building Android roms since 2012 for various devices including multiple Sonys, Lenovo Zuk and Oneplus 5 (my current device). You can check the Oneplus 5 development thread here: Oneplus 5 thread
Jaguar rom is focused on hardening of Android and kernel. As such, the rom has hardened bionic and tightened security. Kernel has security features ported from linux kernel 4.14.
Otherwise, the rom has all standard+ features that come with custom roms:
1 Rom control with custom Power menu, Statusbar, Buttons, Navbar, Quicksettings, Lockscreen, Notifications, Gestures, Themes etc.
2. Working FDE encryption, which is not forced, but could be enabled within Settings
3. Heavily modified Art, Bionic System/Vold and System/Security
4. Telephony response ('silently acknowledged') to Type Zero sms disabled
5. Toggle to disable Captive Portal logging
6. Rom could be booted on locked bootloader out of the box
7. All customizations as listed in '1'
8. MicroG ready
Instructions:
1. If you are encrypted on any other rom, you need to do a factory reset in TWRP, the option, where you enter 'Yes' to confirm.
2. Reboot into TWRP (after factory reset), transfer Jaguar to internal SD, wipe system/cache/data and /vendor, if you have it;
3. Flash the rom and reboot.
You will be unencrypted. If you want encryption (FDE, not ICE), encrypt withing Settings.
Rom V1 is in the attachment. All subsequent release will be posted in #3.
XDAevDB Information
JAGUAR R, ROM for the OnePlus 3
Contributors
optimumpro
Kernel Source Code: Kernel
ROM OS Version: 11.x R
ROM Kernel: Linux 3.x
ROM Firmware Required: Unlocked Bootloader, if Magisk is Required
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 1
Stable Release Date: 2021-01-04
Created 2021-01-04
Credit: AOSP, Lineage, DU, MSM-Xtended, Crdroid
Reserved
January 8: New release, V2.0
1. January security patches
2. Rom rebuilt with speed flag. As a result, it is larger in size, but should be speedier, because there is less runtime compiling involved
Will try it out & report. Many Thanks for keeping our OP3/3T alive. Appreciate all the great developers work on XDA.
Update - Added a few screenshots. Everything is working so far. Snappy & Tons of Customization options. Rooted(Magisk Canary).
Update - Hotspot is not working for me. Typically I do not use this feature so I don't test this function.
kash_si said:
Will try it out & report. Many Thanks for keeping our OP3/3T alive. Appreciate all the great developers work on XDA.
Update - Added a few screenshots. Everything is working so far. Snappy & Tons of Customization options. Rooted(Magisk Canary).
Click to expand...
Click to collapse
How about hotspot? work on both 2.4ghz & 5ghz?
does it work for oneplus 3t too or only oneplus 3.thanks
agustinustjahyo79 said:
does it work for oneplus 3t too or only oneplus 3.thanks
Click to expand...
Click to collapse
Every roms on this sub forum works on both.
I'll give this one a try, see how it is. Will report back later, thanks for the rom
faiz5200 said:
How about hotspot? work on both 2.4ghz & 5ghz?
Click to expand...
Click to collapse
Hotspot is not working for me. Typically I do not use this feature so I don't test this function.
Updated my initial response.
kash_si said:
Will try it out & report. Many Thanks for keeping our OP3/3T alive. Appreciate all the great developers work on XDA.
Update - Added a few screenshots. Everything is working so far. Snappy & Tons of Customization options. Rooted(Magisk Canary).
Update - Hotspot is not working for me. Typically I do not use this feature so I don't test this function.
Click to expand...
Click to collapse
How's the battery life so far? Problems with wakelock?
lapirado said:
How's the battery life so far? Problems with wakelock?
Click to expand...
Click to collapse
I am waiting for @optimumpro to release update with Jan-2021 ASP's. Then I plan to use it as my daily driver.
Currently I have it on my OP3 as a testbed, so can't really provide feedback on battery life. For my OP3/3T over the years average daily SOT has been around 2:30 to 3:30 hours upto & including Android 11.
kash_si said:
I am waiting for @optimumpro to release update with Jan-2021 ASP's. Then I plan to use it as my daily driver.
Currently I have it on my OP3 as a testbed, so can't really provide feedback on battery life. For my OP3/3T over the years average daily SOT has been around 2:30 to 3:30 hours upto & including Android 11.
Click to expand...
Click to collapse
Thanks for the reply.
But that sot seems quite short. Depending on the use you gave, ofc.
But with moderate use, I usually get around 4h.
@optimumpro
So your ROM seems to be build from MSM Xtended sources. There are improvements or advantages in your ROM over the original Xtended ROM?
jaydee 77 said:
@optimumpro
So your ROM seems to be build from MSM Xtended sources. There are improvements or advantages in your ROM over the original Xtended ROM?
Click to expand...
Click to collapse
I used AOSP sources, as well as Msm-Xtended, as well as DU, as well as Crdroid, but:
1. Art, Bionic, System/Vold, System/Security and most of /frameworks/base sources are different
2. Interface is different
3. Some blot removed
4. Several different apps
5. Kernel is different: I squashed about 20 commits (hardening) in one
6. Blobs are different
7. My rom can disable (with a toggle) Captive portal apk, which is spyware. Otherwise, if you uninstall it, you'll have a nasty 'X' in wifi and some sites may not work
8. Acknowledgement of receipt of type zero SMS is disabled. This is is the first thing hackers do - ping your phone with an sms that doesn't appear on screen... .
But ultimately, only you can decide which rom to use.
@optimumpro
My post was not to offend you. Thanks for the explanation and clarification. Your points make sense and they are great and important plus over the other ROMs. This should me mentioned in the OP.
I know that asking for ETA is not welcome on XDA. But one more question concerning updates. What are your plans for that. Your ROM has security in focus. Do you think building monthly updates for Android Security Bulletin?
I don't switch ROMs very often, cos I'm to lazy for this. So when switching to a new ROM I'll like to stick on it for a long time.
jaydee 77 said:
@optimumpro
My post was not to offend you. Thanks for the explanation and clarification. Your points make sense and they are a plus over the other ROMs. This should me mentioned in the OP.
I know that asking for ETA is not welcome on XDA. But one more question concerning updates. What are your plans for that. Your ROM has security in focus. Do you think building monthly updates for Android Security Bulletin?
I don't switch ROMs very often, cos I'm to lazy for this. So when switching to a new ROM I'll like to stick on it for a long time.
Click to expand...
Click to collapse
Usually, once a month. However, this rom is version 1, so, there might be more updates. Definitely, one with January security patches in a few days.
January 8: New release, V2.0
1. January security patches
2. Rom rebuilt with speed flag. As a result, it is larger in size, but should be speedier, because there is less runtime compiling involved
Dirty flash is fine on top of V-1. Download in post #3.
optimumpro said:
January 8: New release, V2.0
1. January security patches
2. Rom rebuilt with speed flag. As a result, it is larger in size, but should be speedier, because there is less runtime compiling involved
Dirty flash is fine on top of V-1. Download in post #3.
Click to expand...
Click to collapse
hotspot fixed in this build?
BrahmaGandhi said:
hotspot fixed in this build?
Click to expand...
Click to collapse
No. - I am using the latest version of TWRP - twrp-3.5.0_9-0-oneplus3
Great to see this hardened flavour of 11 which can even be used with locked bootloader @optimumpro !
As I understand you will have monthly updates also which is great to keep our phone up to date.
One question though; is it possible to use /data/local/userinit.sh scripts with this rom?
Would be a great option to do some system settings without the need of Magisk or other stuff.