Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This is an unofficial Pie build for the S3 LTE (i9305) based on LineageOS 16.0.
!! Please note that all thanks and credits go to @ChronoMonochrome because he ported the necessary changes to t0lte and got Pie to work for that device, especially the kernel thingis!!
And below is a quote from his release, where he mentioned in his t0lte thread all the involved devs and credited to all the people helped to get pie running for our "old" devices.
This work is heavily based on works of PoisonNinja, Option58 (thanks for device tree, kernel and device patches for LOS 14.1).
A full credit for Pie bringup goes to rINanDO (thanks for device tree, kernel and device patches for LOS 16.0).
Click to expand...
Click to collapse
Working
Graphics
Wifi
Data (LTE is not supported currently)
RIL
Bluetooth (needs more testing, receiving files is working, sending I am not sure, also device name needs a change)
Sensors (needs more testing, proximity sensor works, others not sure whether it work)
Vibration
Camera (advanced settings not working switched to snap cam and its working now)
Audio
LED Notification, color and brightness settings
Pico Gapps are working, Youtube and Google Films are well
livedisplay
etc
Not tested, needs testing
Call recording, call forwarding and else
NFC (needs more testing, not sure whether it work)
GPS (got a fix with gps status, first fix lasts a minute, nexts are much faster) currently getting worse, have no fixes 14/03/20
Bugs
feel free to report them, will try to find a solution, but no promise
Download:
ROM
TWRP
Root
Installation:
I am using an older TWRP, which is working fine: TWRP_2.8.7.0_alpha17_by-SdtBarbarossa_i9305.zip
Download the latest build and copy it to the phone
Factory reset in TWRP (Very important! Do not skip)
Wipe cache, Data, System and Dalvik in TWRP advanced (Very important! Do not skip)
Flash LineageOS 16.0
Optional: Flash gapps and root package
Reboot
Be patient. The first boot will take between 5 - 15 minutes.
Enjoy and have fun
Credits:
rINanDO
forkbomb444
Option58
PoisonNinja
AdrianDC
A$teroid
Lord Boeffla
LineageOS team
Nameless ROM
If I miss someone, please PM or post here, and I will add you
Source code: LOS 16.0
XDA:DevDB Information
LineageOS 16.0, ROM for the Samsung S3 LTE (i9305)
Contributors
rodman01, ChronoMonochrome, rINanDO, Option58, PoisonNinja, LineageOS team
Source Code: https://github.com/CustomROMs/android_local_manifests_i9300/tree/lineage-16.0
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.0.x
ROM Firmware Required: TWRP_2.8.7.0_alpha17 or newer
Version Information
Status: Beta
Created 2020-01-15
Last Updated 2020-04-16
reserved
if I need one
reserved
maybe another one needed?
nice job dev @rodman01
Well done
Hi, thanks for your great job!
Almost features are fine. I recognized only two stuffs for now.
** 1) phone call **
I set up a VoIP phone app on a phone which was flashed this rom, and called another phone.
The echo back is heard on the VoIP app side, but I could not hear the voice I talked on the receiving phone.
Do you think above phenomenon is related your attention "Call recording, call forwarding and else" or not?
2) FTU was appeared a few times
When I started using this rom, FTU appeared twice or more after I went through FTU.
But as for now I don't see FTU anymore. Thus, this is a trivial issue.
Anyway, I am looking forward to seeing the next updated version!
small update
Hi There,
gapps pico are working, but graphical glitches are occurring in youtube app, youtube browser is working fine, google films is working fine.
Bluetooth sending and receiving is working, device name is still wrong, shows still Galaxy Note 2, which does not matter and can be changed in settings manually.
Download
lineage-16.0-20200118-UNOFFICIAL-i9305_rodman01.zip https://www.androidfilehost.com/?fid=4349826312261704972
phone call problem was solved! thanks!! :good: :laugh:
super
Fantastic . I will keep an eyes to this.
thank you so much !
trying the rom
What file should I download from the root link ?
new build is up: 20200122
Hi There,
made a new version nd its uploaded now.
Based on yesterday evening leo sources and small update in device source.
- Youtube App is now working and Google films too
No other bigger changes.
And since there are no reports yet about serious problems, I changed the status to from Beta testing to bBeta.
Whats App, Instagram, Facebook and other messengers as well as other social media apps needs testing and would be glad, if someone can report back.
GPS most probably won't work. I am getting no satellites and no fix
Download
lineage-16.0-20200121-UNOFFICIAL-i9305_rodman01.zip: https://androidfilehost.com/?fid=4349826312261708954
Im trying to install this custom rom but everytime I got stuck on LineageOS loading logo forever. Anyone have this problem too?
some problems...
on 20200118 ver.
1) following apps sometimes crashed.
LINE, Adobe photoshop express, Amazon Shopping, Proton Mail.
I felt these apps often crash especially when a first invocation and registering an account to every app via network.
After registered my account, crash frequency decreased.
2) following apps couldn't be installed by Google Play Store
LINE, Google Drive, Google Spreadsheet
* For LINE, I installed older apk manually.
I cannot download 20200121 ver. via AFH yet. I'll test further after the rom is updated.
MagusCoD said:
Im trying to install this custom rom but everytime I got stuck on LineageOS loading logo forever. Anyone have this problem too?
Click to expand...
Click to collapse
Have you wiped out data, cache, and Dalvik cache before install the rom?
If you didn't yet, try it but ALL OF YOUR DATA WILL BE CLEARED!!
Be aware of what you're doing and do everything at your own risk.
I got the same issues .
I keep it stuck there for almost 40 minutes 2 times but it didn't work.
@rodman01
I intend to flash and test the ROM this weekend. However, I've issues to download it as AFH doesn't find any mirror. Do you have another DL available?
Another question: Anything against not to use your given and linked root solution but to use Magisk? As you provide a separate root solution, I assume Magisk is not incorporated into the ROM.
MagusCoD said:
Im trying to install this custom rom but everytime I got stuck on LineageOS loading logo forever. Anyone have this problem too?
Click to expand...
Click to collapse
ximia said:
Have you wiped out data, cache, and Dalvik cache before install the rom?
If you didn't yet, try it but ALL OF YOUR DATA WILL BE CLEARED!!
Be aware of what you're doing and do everything at your own risk.
Click to expand...
Click to collapse
Depending on from which rom you are coming, it could be better to flash an other custom rom first. You can try RR or cm14 and test whether this is working. And if yes, that follow the steps in op for a new and clean installation. It can also depend on the recovery you are using.
ximia said:
I cannot download 20200121 ver. via AFH yet. I'll test further after the rom is updated.
Click to expand...
Click to collapse
Oswald Boelcke said:
@rodman01
I intend to flash and test the ROM this weekend. However, I've issues to download it as AFH doesn't find any mirror. Do you have another DL available?
Another question: Anything against not to use your given and linked root solution but to use Magisk? As you provide a separate root solution, I assume Magisk is not incorporated into the ROM.
Click to expand...
Click to collapse
Sorry for the issues with afh. I will try to fix it with uploading the version again.
@Oswald Boelcke no specific reason why I linked the root to leos. Magisk should work as in previous versions. I tested it a couple of weeks ago with a prototype version and it worked. So its worth to try magisc, yes.
Rom new uploaded, afh should find mirror now. Sorry for circumstances:
lineage-16.0-20200121-UNOFFICIAL-i9305.zip: https://androidfilehost.com/?fid=4349826312261708954
rodman01 said:
Rom new uploaded, afh should find mirror now. Sorry for circumstances:
lineage-16.0-20200121-UNOFFICIAL-i9305.zip: https://androidfilehost.com/?fid=4349826312261708954
Click to expand...
Click to collapse
Affirmative, just downloading. Thanks a lot!
ximia said:
on 20200118 ver.
1) following apps sometimes crashed.
LINE, Adobe photoshop express, Amazon Shopping, Proton Mail.
I felt these apps often crash especially when a first invocation and registering an account to every app via network.
After registered my account, crash frequency decreased.
2) following apps couldn't be installed by Google Play Store
LINE, Google Drive, Google Spreadsheet
* For LINE, I installed older apk manually.
Click to expand...
Click to collapse
I could install all your mentioned apps via google play store. It last a bit, the download is not fast, but worked on my end. Amazon is crashing on my side too, the others not, but I haven't tested them much, because I don't have accounts or ids for for example photoshop express or want to create or share my phone number or personal details.
Related
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 2.3 (Gingerbread), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
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.
Instructions:
First time flashing CyanogenMod 7 to the HTC Aria, or coming from another ROM?
Root the device and install ClockworkMod Recovery. Instructions are available here.
Perform a NANDroid backup of your current ROM.
Format the system, data & cache partitions of your device.
Perform a factory reset.
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Upgrading from earlier version of CyanogenMod 7?
Perform a NANDroid backup of your current ROM.
Flash CyanogenMod (your Google Apps will be backed up & restored automatically).
Issues?
Experience issues? Please provide the following info:
If the device was hard reboot, please provide the file "/proc/last_kmsg".
If the device was soft reboot or is "bootlooping", please run a logcat and provide the full output.
Please use Pastebin when possible.
Download Links:
Official post
CyanogenMod:
Latest version: update-cm-7.1.0-Liberty
Download: link
Mirror: link
MD5sum: 006197debecd916dc8ce3feadea1e74a
Google Apps addon:
Version: gapps-gb-20110828
Mirror: link
Mirror: link
Version: Google Talk with video addon
Mirror: link
Mirror: link
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
hey, just want to say… GREAT JOB GUYS. YES, THANK YOU SO MUCH FOR THIS AWESOME ROM!!!
Looking good so far. Will post if I run into any issues. Glad I can finally have a stable build and not need to flash for a little while!
Thanks for all the effort.
Having issues with data. It worked fine for a while on the first boot but once I rebooted the phone, I can't get the phone to connect on data. Anyone having this issue, and most importantly how do I resolve it?
Other than that, amazing. Thanks for this great rom.
Edit: I looked into the access point name under the mobile network section and noticed a bunch of info was wrong. Notably the password was missing. I added the password and rebooted the phone and now everything is working fine. FYI the password is CINGULAR1.
android market wont let me download aanything!!! Please help!
_jfo_ said:
Having issues with data. It worked fine for a while on the first boot but once I rebooted the phone, I can't get the phone to connect on data. Anyone having this issue, and most importantly how do I resolve it?
Other than that, amazing. Thanks for this great rom.
Click to expand...
Click to collapse
No issues here.
supetawesomedude said:
android market wont let me download aanything!!! Please help!
Click to expand...
Click to collapse
Again, not any issues here.
supetawesomedude said:
android market wont let me download aanything!!! Please help!
Click to expand...
Click to collapse
clear data and reboot?
Installed over an old nightly fine, no problems whatsoever after a full day of use.
Nice work guys.
brswattt said:
clear data and reboot?
Click to expand...
Click to collapse
What the heck? It's workking first fine now!
thnxz. looking good
Hmm...i wanted to try using this "juwe" script but it won't boot...i'm assuming some sort of conflict with darktremor. I also wanted to go to S2E but the last time i tried to go from DT to S2E, everything went haywire and i had to restore an old back up because i rookishly forgot to make one before i started fuxing with S2E...hmph guess i'm stuck with 8-9-1 & DT...life goes on though...
zervic said:
Hmm...i wanted to try using this "juwe" script but it won't boot...i'm assuming some sort of conflict with darktremor. I also wanted to go to S2E but the last time i tried to go from DT to S2E, everything went haywire and i had to restore an old back up because i rookishly forgot to make one before i started fuxing with S2E...hmph guess i'm stuck with 8-9-1 & DT...life goes on though...
Click to expand...
Click to collapse
Your best bet would be to do a Titanium Backup of all user apps, install the ROM fresh, then install S2E, reboot, then restore the backups of user apps and your S2E transition is complete.
Sent from my Liberty using XDA Premium App
^^^ titanium is godly! S2E is worth it, imo. do a fix permission in ROM manager afterwards and a couple re-boots and bam! Butter smoothness
Anybody with the vibration mode not working when receiving calls? I turned vibrate on pretty much everywhere and yet when receiving call, the phone does not vibrate. However, it does vibrate when I receive a text message. Help!
Sent from my Liberty using XDA App
EDIT: I just toggled from the "Default" profile to "Work" and then back to "Default" and now it works. Strange...
Very legit! My girl loves Cynogen!
Almost did a battery pull on first boot. Coming from an older Nightly. Right as I was pulling off the backplate though, the screen went dim and the keys lit up, and everything loaded. So be patient guys on first boot.
My you guys have been busy. Very polished, so many new features.
Just came back to CM7 after about 3 mo. on the Sense ROM. I use GPS constantly, so I have been testing it extensively today. Happy to say Maps, Nav, and this geotagging app I have all work really well.
Zero problems so far, congrats!
Ok guys (and girls), here's a problem I've been dealing with for over a week now. Any help would be appreciated. I have been keeping up with the nightly builds and on nightly 213 and forward (including this stable release), I have found that my phone will stop receiving data after around 8 hours after a reboot. The only way for the data to work again is to reboot. This occurs on both mobile data (3G) and wifi connections. I have rolled back to nightly 208 and the problem doesn't occur. I have uninstalled all new apps since this started occurring, so I know it is not an application problem. I installed 7.1.0 stable with a full wipe, so that's not the problem. I don't think it is similar to the problem reported in post #4 of this thread because my Access Point information under Mobile network settings are the same in my working N208 as they are in the non-working 7.1.0. Also, neither version had a password, so following the directions in post #4 I put in the password CINGUALR1 on the 7.1.0 stable version, and the problem still persisted.
I am running DC's 8.9.1 and Juwe's RAM script, though I have been told neither of those could be the culprit.
Any suggestions, please?
something with your setup - have been running since last night and have not rebooted since and have had no connectivity issues at all.
What's the earliest nightly build that has the problem for you?
Did you format your system partition before the clean install?
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4.4 (Kitkat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we 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. You will need to provide your own Google Applications package (gapps). 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 our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions
First time flashing CyanogenMod 11.0 your device, or coming from another ROM?
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe data & cache partitions of your device (required when coming from stock!).
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Known Issues
* None
Other Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread. "I'm having problems rooting/unlocking" is NOT relevant here.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
Experience issues?
* Nightlies: bug reports are not accepted. You are relying on yourself and your peers in this thread for support!
* M-series: file a bug in Jira.
Download Links
CyanogenMod: download.cyanogenmod.org
Google apps addon:
Download: http://goo.im/gapps (use latest kk gapps)
Mirror: http://download.crpalmer.org/downloads/gapps/
Useful Links
Unofficial changelog
Picassowifi wiki
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
CyanogenMod 11.0 for Tab Pro 10.1 PicassoWiFi, ROM for the Samsung Galaxy Tab Pro 12.2, 10.1, 8.4
Contributors
crpalmer
Version Information
Status: Stable
Created 2014-09-26
Last Updated 2014-09-25
Reserved
Reserved
@crpalmer, let me be the first to congratulate you on this! It's amazing how we have official CM support now!
Thank you very much!
Congrats again on your hard work paying off, and making it into AP. http://www.androidpolice.com/2014/0...-extended-to-the-samsung-galaxy-tab-pro-10-1/
Nice work. Think I'm about ready to do my first flash. . :good:
Congratulations on being official
It's with great interest I have followed the development of your T-520 version of the cm11, even though I don't have one myself. Why? Firstly, I'm amazed by the short time frame in which you actually accomplished this, and conquered the Exynos SoC. But, I'm also A proud owner of a T-900, and from what I can tell there is only the screen size that differs the T-520 from the T-900. In my mind, it should be feasible to port, though I might be wrong.... Maybe, you have some ideas of how to correct/evolve Shaheen's port of your ROM. Who knows, maybe at this point you're bored and need a new challenge, as the major obstacle is breached and, before the work with Android L begins... Besides, neither Shaheen, nor you own a T-900, why this should be a very simple task:laugh:
The current error report is as follows:
arcadia2uk said:
Thanks for reviving this one Shaheer,
After some problems in getting the full ROM onto the drive (all on my side), I finally got it up and working. The ROM is a lot snappier that prior versions, and is stable over all. Below is my summary of working/non-working functions. Additionally, with the all new TWRP 2.8.0.0, see post #55, the format of system and cache are instant, why ROM testing is a breeze.
I have noticed the following issues:
- WiFi connects, but loses password on reboot, same issue as earlier build
- Bluetooth: devices are seen, but do not connect - Error message: Can't connect
- External SD is not detected by device - see post #54, below, for more detailed info
- mtp - device does not mount on PC
- adb - device does not mount on PC
- Camera is broken - Error message
- Torch is broken - Error message
- Lid sensor - No reaction
- Capacitive lights - No reaction
- Sensors - No reaction
- IR blaster - No reaction
- Offmode charging - but it will not work on the picasso-wifi either, at least until tomorrow, 20140926
- Home button doesn't work correctly. It wakes up the device, but does not go to the home-screen
- Battery drain is significant - However, it might be my impression from heavy use of the screen while testing
Only two outstanding items (non-tested) from the list Shaheer posted below. I would appreciate if someone would test them and confirm if they are working, or not:
- Miracast displays - Most likely functional, given that the Chromecast dongle is working | Best Guess: yes
- Google Play Movies: downloading a video and then playing the downloaded copy. Apparently, crpalmer has received a CyanogenMod commit and the issue is fixed as of now, 20140925 | Best Guess: No
Click to expand...
Click to collapse
Anyhow, we (T-900 owners) would really appreciate your input, and I believe speaking for Shaheer as well, and to tap into your substantial knowledge and experience.
Once again, I'm really impressed by your accomplishments, and I sincerely congratulate you to the well deserved status as an officially recognized cm-developer.
Finally, if a tester is needed, I'll be around.
Thanks in advance.
Congrats! I appreciate your hard and nice work. Thanks :good:
I am so thrilled to see official CM support for Galaxy Tab PRO 10.1. Ordered mine couple of days.. and still in transit. They day I ordered.. I am thinking how will i live with touchwhiz..
I guess now i don't have to worry.. will root and flash right away once its here. Looks like everything is working. I don't care about small bugs if battery life is as good as stock
Thanks again
Good work !
I am on GraveD stock ROM, running very well for a month.
But I plan to try CM11 asap.
Sent from my SM-T520 using XDA Free mobile app
Subscribed in hopes this will trickle back to klimtwifi (Tab S with Exynos 5420)
Wow, thanks for the great news @crpalmer!
WiFi easy fix
sorry wrong thread
@crpalmer,
I followed the instructions "How To Build CyanogenMod Android for Samsung Galaxy Tab Pro 10.1 Wi-Fi ("picassowifi")" (http://wiki.cyanogenmod.org/w/Build_for_picassowifi).
I faced issues with drmserver and gpsd on extract-files.sh : "Permission Denied"
I managed this by copying them to internal memory and them adb pull to their destination locations.
It's compiling now...
Which ir app are you guys using? I can't find one that works.
If you want to disable the soft buttons and use the on-screen buttons (I use the tablet a lot in portrait mode and the soft buttons get in the way all the time).
1. Enable soft keys : edit the /system/build.prop file to include the following line qemu.hw.mainkeys=0
2. Disable the soft keys : edit the system/usr/keylayout/sec_touchscreen.kl file and add # in front of the two lines
3. Turn buttons light off : go to settings -> buttons and disable backlight
4. Reboot
I don't think it was posted all in one place before.
cviniciusm said:
@crpalmer,
I followed the instructions "How To Build CyanogenMod Android for Samsung Galaxy Tab Pro 10.1 Wi-Fi ("picassowifi")" (http://wiki.cyanogenmod.org/w/Build_for_picassowifi).
I faced issues with drmserver and gpsd on extract-files.sh : "Permission Denied"
I managed this by copying them to internal memory and them adb pull to their destination locations.
It's compiling now...
Click to expand...
Click to collapse
Hmmmm. That's a good one. Very few vendor blobs tend to have restricted read permissions but apparently we hit two of them. I assume that it was actually drmserver.samsung though right? That's important if your build is going to have working DRM.
I made myself a note to figure out how to make that work better and/or document it better.
FYI, you can also download an existing build, unzip that file somewhere, and then run
./extract-files.sh /path-that-you-unznipped-to/
and it will pull all the files from that unzipped directory.
burnski said:
Which ir app are you guys using? I can't find one that works.
Click to expand...
Click to collapse
I currently like Smart IR Remote. It's not free but they seem to be good people and I appreciate that.
crpalmer said:
Hmmmm. That's a good one. Very few vendor blobs tend to have restricted read permissions but apparently we hit two of them. I assume that it was actually drmserver.samsung though right? That's important if your build is going to have working DRM.
I made myself a note to figure out how to make that work better and/or document it better.
FYI, you can also download an existing build, unzip that file somewhere, and then run
./extract-files.sh /path-that-you-unznipped-to/
and it will pull all the files from that unzipped directory.
Click to expand...
Click to collapse
Hello,
Thanks.
Unfortunately, I need more RAM, only 2 GB RAM and 2 GB Swap don't fit the load.
crpalmer said:
I currently like Smart IR Remote. It's not free but they seem to be good people and I appreciate that.
Click to expand...
Click to collapse
Cool thanks I'll check it out
Did you get Infra Red ever to work? I use Touchsquid and it always worked with every ROM i tried.
But in CM11 it looks like it is broken. Maybe I am too impatient and i should wait a bit for CM to get IR working and go back to GraveD's ROM for a while.
Thanks for the hard work crpalmer!
Code:
Code:
/*
* Your probably long expired 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
* and point my finger right back at you.
*/
Installation Instructions
Make sure you have a second partition on your SD card before flashing!!!! This can be created with minitool partition wizard on Windows or gparted on Linux.
If on a BML rom (stock-based GB)...
0. Read "Things to take note of" below
1. Reboot to recovery
2. Make sure your version of CWM is at least 5.x
3. Install zip. It will reboot a couple of times, don't be worried.
4. If you want root or Gapps, flash them now
If on an MTD rom (CM7 and all ICS+)(I tested CM9, CM10.1 and CM11)...
0. Read "Things to take note of" below
1. Reboot to recovery
2. Wipe data, and cache paritions (just in case). If updating to a newer build, you can probably skip this step
3. Install zip
4. If you want root or Gapps, install them now
The first boot can take several minutes. Be patient. If it takes 10+ minutes, pull the battery and reboot to recovery.
Things to Take Note Of
Humberos (the i9000 maintainer) has moved on to different projects which means no first-gen Galaxy S devices are being actively maintained. Builds may break at any time!
I actually have a T959P, not a T959V... It was released by Telus in Canada. It is a very similar device (I can run ROMs for the T959V with limited problems - ie sometimes I get wakelocks and the gps never works), it has a different GPS chipset and also uses different cell bands (but I can still use your guys modems but I lose access to the 850Mhz band). I have created a build specifically for the T959V as best as I can guess and also provide T959P builds.
The USB connection is MTP and not mass storage as Omni has removed mass storage. In recovery there is still an option to mount as mass storage device.
This build is very close to the official omni source code. This means that the recovery is TWRP and there aren't any added "features"
In order to get it rooted, you need to install SuperSu.
Gapps reportedly slow down the device significantly so tread carefully.
Backup Backup Backup! I'm not responsible for you losing any data.
Working
Taking pictures
RIL
SMS
Data
Recovery
Bluetooth
Wifi
Vibration
Powered-off charging animation
Flash from BML
Video Recording
Automatic Brightness
Moving Apps to the SD Card
GPS
Encryption
Compass
SElinux in enforcing mode
What probably doesn't
Microphone mute option doesn't work during calls
What doesn't
720p recording is very laggy
What's been removed
TV-Out - It was removed upstream plus I think binary blobs are broken in Lollipop...
Live wallpapers - this is a low-ram device
Everything else is not tested!!!
XDA:DevDB Information
Unofficial OmniRom 5.1 for the Galaxy S 4G (T959V) and Galaxy S Fascinate 4G (T959P), ROM for the Samsung Galaxy S 4G
Contributors
xc-racer99, humberos
Source Code: http://github.com/omnirom
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
ROM Firmware Required: All
Based On: OmniRom
Version Information
Status: No Longer Updated
Created 2015-06-30
Last Updated 2016-05-12
Thanks Time!
This would not have been possible without the following people:
Thanks to humberos for bringing Lollipop to the first-gen Galaxy S series. This would not have been possible without his work.
Thanks to FB and Dao for their work on the CM-11 device tree. I used several of their fixes.
Thanks to noiphonehere for his device trees and kernel, most of my work was based off of his.
Thanks to bhundven and the other members of teamacid for their work on the aries kernel.
Thanks to all others that have helped get this phone to where it is today!
Thanks to vcmerritt. A name you're probably not familiar with, but he was the only one to create something for the T959P and without him I'd still be on stock...
Build your own!
Follow the instructions at http://docs.omnirom.org/Setting_Up_A_Compile_Environment using the android-5.1 branch
Before doing a repo sync, put the galaxy_s_series.xml file from the Download folder in .repo/local_manifests folder of the source tree.
After syncing the source, open a terminal and in the directory where you downloaded the source code type "source ./build/envsetup.sh" and then "brunch galaxys4gmtd"
Changelog
Changelog for 07/03/2015 Build
Newer Omni source
Added volume controls and flight mode toggle to power button menu
Added Bigmem option. This increases available RAM by ~20mb but breaks 720p video recording. Humberos created the kernel setup and I integrated a toggle for it into Advanced device settings.
Selinux is now in enforcing mode. I had to modify the GPS startup to have any chance of getting here. Please let me know if it still works/doesn't work/never worked
Notifications are sometimes wonky. To fix, in Settings, go to Performance, then Advanced. Select Force high-end graphics and reboot your phone.
Changelog for 2015/07/20 Build
The data partition is now the second partition of the SD Card as opposed to internal storage
Gapps now work. If you get error 461 when installing from Play Store, a full data wipe should fix it. You can try experimenting with clearing data for the Play Store and/or Play Services or removing and re-adding your Google account if you don't want to do a full data wipe.
HSPA vs UMTS settings in DeviceSettings has been fixed
High-End graphics are forced by default to fix notification issue
ART parameters have been tweaked
Miscellaneous other tweaks, see my Github for details
Changelog for 2015/07/24 Build
Stabilized bluetooth connection
Fixed typo in GPS initialization. Does it work?
Added ability to use f2fs file system on /data. Supposed to give better performance
Added force fast charge and touch wake to kernel. Touchwake is accessible through its sysfs path, fast charge through Performance Settings, BatterySelinux currently denies these requests...
Changelog for the 2015/07/29 Build
This is a maintenance build. Very little has changed
Some more RAM freed (disabled some debugging stuff, TV-Out driver, IR driver)
Sepolicy updated for fast charge and touch wake
GPS initialization tweaked - unsure if works. If it doesn't, a dmesg would be appreciated
Changelog for 2015/08/02 Build
SElinux changed to permissive - this build only
GPS sepolicy changed - unsure if all necessary things are implemented
Changelog for 2015/08/13 Build
Selinux back to enforcing. Thanks to @anoymonos for the dmesg and @DerPugNa for offering to send me one as well
Fixed encryption
Changelog for 2015/08/31 Build
Updated Android version (5.1.1_r5 to 5.1.1_r12)(upstream Omni Change)
Restoring /system in TWRP should now work
When installing from BML, a chance is given to install gapps and/or SuperSu before rebooting
zRam is now actually used...
Changelog for 15/10/2015 Build
Fixed typo in updater.sh (thanks @FBis251!)
Update Omni source code - plenty of little tweaks since last build
Source Code and Downloads
Main Source
http://github.com/omnirom
Device Specific Source Code
http://github.com/xc-racer99/android_device_samsung_telusgalaxys4gmtd for the device tree (see android-5.1-t959v branch)
http://github.com/xc-racer99/android_device_samsung_aries-common for the common device tree (see android-5.1 branch)
http://github.com/xc-racer99/android_kernel_samsung_aries for the kernel (see android-5.1 branch)
http://github.com/xc-racer99/proprietary_vendor_samsung for the prop blobs (see android-5.1 branch)
Downloads!
All builds are found at https://drive.google.com/folderview...VVSzJxYVU3eHlWZGR1VVNZUWk1V1QzOUk&usp=sharing
Please let me know if the link doesn't work! There are also builds there for the T959P, in case there are any users of it left.
Gapps
Gapps do not work on builds prior to 2015/07/20. On more recent builds, they can be installed from http://forum.xda-developers.com/showpost.php?p=59731008&postcount=2
SuperSu
SuperSu can be found at https://download.chainfire.eu/696/SuperSU/
Thanks thanks ....
Awesome work @xc-racer99!
Wow, bringing this ole device back from a coma here. Nice to see someone else willing to work on lollipop for this oldie but goodie. Keep this device alive man.
Edit: If you are in need for some GFX for this thread, let me know and I'll see what I can brew up for you.
GFX.myst. said:
Wow, bringing this ole device back from a coma here. Nice to see someone else willing to work on lollipop for this oldie but goodie. Keep this device alive man.
Edit: If you are in need for some GFX for this thread, let me know and I'll see what I can brew up for you.
Click to expand...
Click to collapse
I hope I can keep this great little device going a little longer, however it will probably get tough. I did a repo sync earlier today and things are starting to break. The last few builds haven't even booted. With humberos no longer maintaining the i9000 and aries-common, I've had to fork the aries-common repository to try to keep going. The only upside of this is that I now have a little bit more freedom and can add things in if I want to.
Thanks for the offer of the graphics. If I can get a new build working, then I'll probably take you up on your offer. I think I've traced the problem but I'll have to wait and see...
For anyone that is trying/has tried this out, I'd be very curious on the status of the GPS on the T959V. I'm interested in creating the sepolicies for it so we can put selinux into enforcing mode but I don't want to go to the effort if it doesn't even work right now.
I've downloaded the zip and one of the smaller Gapps packages...won't be able to flash until early next week...I'll be out of town...will post results later...thanks for keeping this phone current.
New Build Uploaded!
Download is still at the same link as before, just use the 2015-07-03 build
I managed to find out why my new builds hadn't been booting - it was because the syntax for using a custom kernel toolchain had changed.
Anyway...
Changelog for 07/03/2015 Build
Newer Omni source
Added volume controls and flight mode toggle to power button menu
Added Bigmem option. This increases available RAM by ~20mb but breaks 720p video recording. Humberos created the kernel setup and I integrated a toggle for it into Advanced device settings.
Selinux is now in enforcing mode. I had to modify the GPS startup to have any chance of getting here. Please let me know if it still works/doesn't work/never worked
On another note, I've had a look at re-implementing TV-Out support. It doesn't look promising as several of the functions in the android frameworks that it used have been tweaked.... Still working on it but don't hold your breath.
Also, if somebody could test dock audio that would be appreciated. I don't have any way of testing it. If it doesn't work, I do have an idea on how to fix it (for those interested, another almost-aries device, the Infuse 4G, had to modify things slightly to get it to work. I would try to emulate their solution).
Omg download nowwww....thanks my friend
Alright, I'm having some issues on the latest build with notifications and the lockscreen. I'm still working on tracing down the reason for the problem...
DickyG said:
I've downloaded the zip and one of the smaller Gapps packages...won't be able to flash until early next week...I'll be out of town...will post results later...thanks for keeping this phone current.
Click to expand...
Click to collapse
Hello, im a user of a t959v. And I've been using this rom for three days. Everything is fine and very smooth on this rom except that, I can't install anything from the playstore. I always get (cannot install app due to an error 963). And Ive tried all the gapps, even the new link provided but still no luck.
billowusu47 said:
Hello, im a user of a t959v. And I've been using this rom for three days. Everything is fine and very smooth on this rom except that, I can't install anything from the playstore. I always get (cannot install app due to an error 963). And Ive tried all the gapps, even the new link provided but still no luck.
Click to expand...
Click to collapse
Good to hear that that's its (mostly) been working for you. I was hoping that the gapps problem was just me
Out of curiosity, which of the alternate gapps did you try?
A brief google of the error brings up a couple of possibilities...
Try an older gapps version. The ones from devloz on the i9000 thread devloz and the oldest revision for 5.1.1 are probably your best bet. Please be aware that Google Play store will automatically update!!! In order to prevent this, you will need to create a folder called "com.android.vending-1.apk" in /data/app (use a root explorer such as ES File Explorer or adb if you know how). If a file with that name already exists, delete it first.
Another thing to try would be to unmount your sdcard first before trying to install an app. I know, its a terrible work-around but it should work. This is because the error is that Google Play is trying to save some data on your sdcard but then for some reason it fails (I'm not sure why).
I'll hopefully get around to seeing if its a permissions problem after I find out what's been causing the issue with the notifications on the latest build.
P.S. Does the GPS work?
Early update...
...ROM flashed fine...a little slow to boot...about 3 minutes...but it booted.
...Gapps flashed fine...used 20150513_5.1.x package
...Installed Super SU (although I don't think that's necessary) and TB.
...So far only gave a quick test to camera and web browser...no problems.
...Am now in the process of re-installing user apps and data from TB...this will take a while.
When I'm done with that, I use Link2SD to link most of my user files to the SD card. After that is all set up, I'll test stuff like GPS, root access, etc. I'll post back later...maybe tomorrow.
But so far so good.
OK...I did some testing tonight and here's some results.
Working:
.it boots
.root
.browser
.playstore
.camera
.link2sd (about 180 mb free in internal)
.camera
.wifi
.email
Nor working:
.bluetooth
.google search/voice search
.just about all the rest of the Gapps
.tons of force closes including Maps so can't test GPS
Won't be able to do anymore testing until next week.
DickyG said:
OK...I did some testing tonight and here's some results.
Working:
.it boots
.root
.browser
.playstore
.camera
.link2sd (about 180 mb free in internal)
.camera
.wifi
.email
Nor working:
.bluetooth
.google search/voice search
.just about all the rest of the Gapps
.tons of force closes including Maps so can't test GPS
Won't be able to do anymore testing until next week.
Click to expand...
Click to collapse
Alright, thanks very much for the update. I'll do some more testing here and see if I can solve anything. For me, bluetooth file transfers to the phone work but not from the phone.
I've been looking at the notification "error" where the lockscreen notifications do not appear correctly. It appears to have been introduced upstream with a merge. I'm having difficulty finding out exactly what changed and since no errors are being thrown in the logcat, it could be a while...
For testing the GPS, there's an app from the Play Store called GPS Test which does a nice job of showing satellites and whether or not you have a lock on them.
you're the man!
nice one! its nice that this device are still alive.! and now were on 5.1
DerPuGNa said:
nice one! its nice that this device are still alive.! and now were on 5.1
Click to expand...
Click to collapse
No, it should be Humberos is the man! I basically re-hashed his code for the i9000 and used bits and pieces from people like Bhundven, noiphonehere, maxfierke, Dao, and FB to get things to work properly.
For a status update, I figured out the lockscreen notification problem. I have a new build being made that I hopefully will be able to upload in the next couple of days (internet dependent). TV-Out looks totally broken as the proprietary blobs no longer function. I don't have the know-how to make ugly hacks to get them to work. The new build will have SElinux in enforcing mode and have the different GPS initialization (like the last build) until someone tells me that it doesn't work
Uh-oh, looks like I jumped the gun.... Having problems once again
Any updates on getting the play store to work? I have searched, downloaded, and tried every gapp made for 5.1. I found that I can load any app on the rom, if I get the APK version of it.
AgainstTheFlow said:
Any updates on getting the play store to work? I have searched, downloaded, and tried every gapp made for 5.1. I found that I can load any app on the rom, if I get the APK version of it.
Click to expand...
Click to collapse
Darn, so its still not working. Not surprising. I've been struggling on the notification issue and am at my wit's end as to what the problem is. I don't think its only our phone as several i9000 users have been reporting it as well. Whether it is only the first-gen Galaxy S series that is having the problem or not is anyone's guess. My programming skills are insufficient to fix the issue!
I'll have another look at gapps over the next couple of days and see if I can figure out a combination that works 100% of the time.
I'm assuming the error message is still 963 or does it silently fail now? Its probably related to the fact that we have only an external sd card and no internal sd card like most devices...
All the problems with the notifications that I've found are:
Only one notification will show up at a time
Large notifications such as the music player do not render properly. They are cut off at the normal notification size and occasionally it seems as if there are two layers there (one for the small version, one for the bigger version) (see attached picture, taken with VLC as the media player, but also appears with Apollo)
Notifications don't always show up. A little icon appears in the top left corner of the status bar but no notification is present. Seems hit or miss
The words No notifications appears in the lockscreen just above the clock when there are no notifications. Otherwise, a notification (and only one) which can't be clicked covers part of the clock
SRGX2 for Life One X2 MiniThis Rom Is a Stripped down modified version of the Life One X2 Mini stock Rom.
NOTE: After installation give Launcer 3 notification permission and update Google Play Services (click on the notification).
(Please remember I do this in my free time and with my own money. If you like it please hit the thanks button)
Mods:
Malware removed
Build.prop Tweaks
Oreo Launcher
Camera app replaced by OpenCamera
File manager replaced by MiXplorer
To do list:
Build wifi drivers into the Kernel
Strip down rc scripts
What Works:
Boots
Calls
SMS
Data
GPS
Wifi
Bluetooth
Audio
Video Playback
Sensors
Led
Camera
Flash
Fingerprint
Not Working Yet:
(You tell me)
Downloads:
Current Build: https://www.androidfilehost.com/?fid=673956719939824825
Builds: https://www.androidfilehost.com/?w=files&flid=239712
Patches: https://www.androidfilehost.com/?w=files&flid=254440
TWRP: https://drive.google.com/file/d/0BzMHnGbQH3bhTERvcGxlSkZFa2M/view?usp=sharing
Kernel: https://github.com/vampirefo/android_kernel_blu_kernel_x2 (Special thanks to @vampirefo for the kernel source)
Screenshots: comming soon
Changelog
Version: Testing
Build: 01072018211020
Initial release
Version: rc1
Build: 01142018205847
switched to stock theme
Version: 1.1.0
Build: 02182018215948
rebuild off of the 01/04/2018 update
Version: 1.1.1
Build: 02242018165134
fixed mobile data bug
Version: 1.1.2
Build: 03032018224915
changed DPI to 441
added stock calendar app
added stock calculator app
add stock clock app
Troubleshooting
reserved
Does quick charge work?
Been running for a couple of days now without issue.
cyrusharding said:
Does quick charge work?
Click to expand...
Click to collapse
Yes it works, I've beeen using 2 QC3 chargers with no problems at all.
Awesome, works great so far. Here are a few things I noticed :
1- Keyboard didn't show up easily during setup, but eventually it became smooth
2- Following apps did not install (Package Helper error) : Fitbit & Spotify. Spotify was a known issue in stock rom but Fitbit was working fine in stock.
3- Netflix is not available. Previously I had LineageOS 13 and I was able to install Netflix. I know they banned uncertified devices, but I was still able to get it with that rom.
4- Fingerprint is not working 100%. I am able to unlock the device with it but apps are not able to use it properly. For example try Starbucks or any banking app. They will ask if you want to use fingerprint, you say yes and you put your finger, some apps crash, others will say fingerprint recognized, but then they don't actually store/use that fingerprint? Something must have gone wrong... LineageOS 13 also had this issue, but stock rom did not.
I would like to know if it's possible to not have the customizations you did for colors. Blue (pun not intended) hurts my eyes and transparency doesn't look great with some apps open. Also, if you go to device encryption, because you changed colors, some foreground and background colors are now identical and I wasn't able to read the options... I think that screen was the one for if I wanted to ask for password when the device boots.
Also do you have a git for the source tree? I'm learning to build Android and am hoping to see how you are doing things?
Thanks again and keep it up!
enduo said:
Awesome, works great so far. Here are a few things I noticed :
1- Keyboard didn't show up easily during setup, but eventually it became smooth
2- Following apps did not install (Package Helper error) : Fitbit & Spotify. Spotify was a known issue in stock rom but Fitbit was working fine in stock.
3- Netflix is not available. Previously I had LineageOS 13 and I was able to install Netflix. I know they banned uncertified devices, but I was still able to get it with that rom.
4- Fingerprint is not working 100%. I am able to unlock the device with it but apps are not able to use it properly. For example try Starbucks or any banking app. They will ask if you want to use fingerprint, you say yes and you put your finger, some apps crash, others will say fingerprint recognized, but then they don't actually store/use that fingerprint? Something must have gone wrong... LineageOS 13 also had this issue, but stock rom did not.
I would like to know if it's possible to not have the customizations you did for colors. Blue (pun not intended) hurts my eyes and transparency doesn't look great with some apps open. Also, if you go to device encryption, because you changed colors, some foreground and background colors are now identical and I wasn't able to read the options... I think that screen was the one for if I wanted to ask for password when the device boots.
Also do you have a git for the source tree? I'm learning to build Android and am hoping to see how you are doing things?
Thanks again and keep it up!
Click to expand...
Click to collapse
try "dogfood spotify" i had same issue and got that to work on the lineageos 13 blox2mini ROM.
cyrusharding said:
try "dogfood spotify" i had same issue and got that to work on the lineageos 13 blox2mini ROM.
Click to expand...
Click to collapse
Interesting, didn't know that exists. I currently just download off of http://download.spotify.com/android/SpotifyAndroid.apk
enduo said:
Awesome, works great so far. Here are a few things I noticed :
1- Keyboard didn't show up easily during setup, but eventually it became smooth
2- Following apps did not install (Package Helper error) : Fitbit & Spotify. Spotify was a known issue in stock rom but Fitbit was working fine in stock.
3- Netflix is not available. Previously I had LineageOS 13 and I was able to install Netflix. I know they banned uncertified devices, but I was still able to get it with that rom.
4- Fingerprint is not working 100%. I am able to unlock the device with it but apps are not able to use it properly. For example try Starbucks or any banking app. They will ask if you want to use fingerprint, you say yes and you put your finger, some apps crash, others will say fingerprint recognized, but then they don't actually store/use that fingerprint? Something must have gone wrong... LineageOS 13 also had this issue, but stock rom did not.
I would like to know if it's possible to not have the customizations you did for colors. Blue (pun not intended) hurts my eyes and transparency doesn't look great with some apps open. Also, if you go to device encryption, because you changed colors, some foreground and background colors are now identical and I wasn't able to read the options... I think that screen was the one for if I wanted to ask for password when the device boots.
Also do you have a git for the source tree? I'm learning to build Android and am hoping to see how you are doing things?
Thanks again and keep it up!
Click to expand...
Click to collapse
I'm doing my mods on the precompiled factory rom. If you go to the Lineage OS thread, Vampirefo has a link to the device and vendor tree he created for his rom. I am considering having two versions of my rom for the Mini. A light theme (stock) and dark theme the one that is out now. Right now the rom is only in testing stage. I enjoy seeing your interest in learning how to do what I am doing, the more developers the better.
Thanks for you feedback, here are some helpful links. I am a Linux user and my links may be geared toward Linux, some things can be done in Windows, but some require Linux.
Lineage OS for the Mini: https://forum.xda-developers.com/android/development/lineageos-13-life-one-x2-mini-t3692814 (has links to his device and vendor tree)
How to compile an Android kernel: https://forum.xda-developers.com/le-2/how-to/guide-compiling-64-bit-android-kernel-t3512749 (I'm still trying to locate the Mini kernel source)
Tool to unpack and repack a rom: https://forum.xda-developers.com/ap...dows-linux-superr-s-kitchen-v3-0-0-0-t3601702
tool for unpacking apks: https://ibotpeaches.github.io/Apktool/
I hope these help you and enjoy
srgrusso said:
I'm doing my mods on the precompiled factory rom. If you go to the Lineage OS thread, Vampirefo has a link to the device and vendor tree he created for his rom. I am considering having two versions of my rom for the Mini. A light theme (stock) and dark theme the one that is out now. Right now the rom is only in testing stage. I enjoy seeing your interest in learning how to do what I am doing, the more developers the better.
Thanks for you feedback, here are some helpful links. I am a Linux user and my links may be geared toward Linux, some things can be done in Windows, but some require Linux.
Lineage OS for the Mini: https://forum.xda-developers.com/android/development/lineageos-13-life-one-x2-mini-t3692814 (has links to his device and vendor tree)
How to compile an Android kernel: https://forum.xda-developers.com/le-2/how-to/guide-compiling-64-bit-android-kernel-t3512749 (I'm still trying to locate the Mini kernel source)
Tool to unpack and repack a rom: https://forum.xda-developers.com/ap...dows-linux-superr-s-kitchen-v3-0-0-0-t3601702
tool for unpacking apks: https://ibotpeaches.github.io/Apktool/
I hope these help you and enjoy
Click to expand...
Click to collapse
This is awesome thanks so much!! I use Windows on a daily basis but I do have a pretty good knowledge about Linux and have set up a build environment in for Android. These links should help me understand what I am missing. I am also happy to continue testing and give you feedback on this ROM as it is currently my daily driver.
New Rom out. It has the stock theme, other than that it is the same.. I haven't decided if I'm going to build two Roms or have the theme be a patch. Maintaining all the different variants of the Rom are getting to be very time and space consuming.
https://www.androidfilehost.com/?fid=889964283620778170
Strange question, but on the original stock rom, I started having issues with the Package Access Helper not working, while installing updates for Paypal, and just straight up trying to install Spotify, even the APK. I did a full factory reset, still did not work. I also installed the custom rom over at BLOX2.com, and the Package Access Helper still would stop working, even after clearing data/cache. I'm just curious if you know if your rom will fix that issue?
Requia77 said:
Strange question, but on the original stock rom, I started having issues with the Package Access Helper not working, while installing updates for Paypal, and just straight up trying to install Spotify, even the APK. I did a full factory reset, still did not work. I also installed the custom rom over at BLOX2.com, and the Package Access Helper still would stop working, even after clearing data/cache. I'm just curious if you know if your rom will fix that issue?
Click to expand...
Click to collapse
Is this without root? I don't know if my rom will fix that, I never used the Paypal app. Your welcome to try and let me know. Also there is LineageOS 13 for the mini which has been built from source.
https://forum.xda-developers.com/android/development/lineageos-13-life-one-x2-mini-t3692814
New rom rebuilt from the 01/04/2018 update.
v 1.1.0
There is a problem with the latest version of SRGX2. Mobile data doesn't work. I work on it this weekend and keep everyone updated.
Here is the fixed rom.
https://www.androidfilehost.com/?fid=818070582850494825
Good news I was able to get Android File Host to make the Life One X2 an official device. I have made a request for the Mini too. For now all the files will be under the Life One X2 device.
Updated rom: https://www.androidfilehost.com/?fid=673956719939824825
It includes the stock Calendar, Clock and Calculator apps. I changed the DPI to 441. Let me know if anyone has any problems with the Playstore. I know that there has been some requests for the stock Camera and file Manager apps. It's hard to please everybody so I added a patch section which may please some.
Code:
/*
* 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.
*/
AospExtended 6.7
Properties
Selinux mode: Enforcing by default
Build type: user
Gapps: not included
Known issues
Some users report non-functional mobile data after clean flash, reportedly works after manually adding APN or dirty flashing from Official AospExtended build
Notes
Dirty flash from Official ROM not tested, backup EVERYTHING before flashing!
Downloads
21.1.2020
Download
Checksum: a83c665feace3066580f2344af38fc1d
Older builds
14.12.2019
Download
Checksum: f44bdbc961fe2b64a281ec0785975f21
23.11.2019
Download
Checksum: a4043774306c86b3968c826b9ca1ba98
13.10.2019
Download
Checksum: d85208f4ead011dc0e9488b9591ac5d6
Working apps
OpenGapps
MicroG
Magisk
JamesDSP
Sources
ROM
Device tree
Kernel
Vendor
Credits
AospExtended team - ROM
dotOS team - device sources
@gadmei.tw - mobile data fix
XDA:DevDB Information
[ROM][UNOFFICIAL][9.0][MIDO] AospExtended 6.7, ROM for the Xiaomi Redmi Note 4
Contributors
Golbinex
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
Based On: AospExtended
Version Information
Status: Stable
Created 2019-11-02
Last Updated 2020-02-04
Reserved
Changelog
21.1.2020
January security patches
14.12.2019
December security patches
23.11.2019
November security patches
Mobile data tryfix - @gadmei.tw
13.10.2019
Initial build
October security patches
Dirty flashed from AospExtended Official without issues.
:laugh:tks, :good::good:
Only upgrade OCT security patch on offical AEX Rom-0822-mido , right?
i will guess AEX 7.0(Android 10) release stable ver. in Jan 2020:laugh:
Any changes
Changelog
grvkrsaini said:
Changelog
Click to expand...
Click to collapse
3rd post above yours.
gadmei.tw said:
:laugh:tks, :good::good:
Only upgrade OCT security patch on offical AEX Rom-0822-mido , right?
i will guess AEX 7.0(Android 10) release stable ver. in Jan 2020:laugh:
Click to expand...
Click to collapse
Device sources are also different because official ones aren't updated at all, so maybe kernel version and behaviour will be little different.
martinknl said:
Dirty flashed from AospExtended Official without issues.
Click to expand...
Click to collapse
Same here. Rom works great and latest security patch is included. Thanks @Developer
A very good rom
Hello,
I've tried this rom, and it's a good idea , it' works fine !
Very thanks for the developers.
Great ROM
I can't see the OTA updates section in settings, if this ROM will have updates in futute where can i download it?
WareWareX said:
I can't see the OTA updates section in settings, if this ROM will have updates in futute where can i download it?
Click to expand...
Click to collapse
OTA is generally not included in unofficial build
WareWareX said:
I can't see the OTA updates section in settings, if this ROM will have updates in futute where can i download it?
Click to expand...
Click to collapse
Updates will be available in this thread, there will be probably one update per month.
Audio playing on multiple outputs
Hi All,
Firstly thank you very much for providing this ROM with the latest security fixes - everything important is working fine and I have also better battery life than in the AOSP Extended 8 ROMs.
However I have one problem that did not exist in the previous ROM. I use AirAudio (in combination with the Magisk AirAudio module) to stream any sound from the phone to a DLNA audio output. Usually when I activate the AirAudio streaming the sound on the phone stops and the output is redirected to the DLNA speaker. In this ROM though the audio plays on the phone and also on the DLNA speaker.
I contacted the AirAudio developers and they responded that this is a problem with an incorrect audio implementation in the custom ROM I'm using as they have seen this before. This is what they wrote:
-------
I assume you have a custom ROM, eg. Pixel Experience installed?
There are some ROMs around at the moment that have a broken implementation of the audio-driver.
Android-devices MUST only play the audio locally _or_ remote via AirAudio, this is defined by Google.
I think you have to wait for an update of your ROM or switch to another ROM like others did :-/
-------
Is this something that could possibly be taken into consideration for a future update as this means I cannot stream audio from all sources (e.g radio apps and Spotify)to any DLNA output.
I really like AOSP Extended and would rather not switch to a different ROM.
Many thanks,
herges
herges said:
Hi All,
Firstly thank you very much for providing this ROM with the latest security fixes - everything important is working fine and I have also better battery life than in the AOSP Extended 8 ROMs.
However I have one problem that did not exist in the previous ROM. I use AirAudio (in combination with the Magisk AirAudio module) to stream any sound from the phone to a DLNA audio output. Usually when I activate the AirAudio streaming the sound on the phone stops and the output is redirected to the DLNA speaker. In this ROM though the audio plays on the phone and also on the DLNA speaker.
I contacted the AirAudio developers and they responded that this is a problem with an incorrect audio implementation in the custom ROM I'm using as they have seen this before. This is what they wrote:
-------
I assume you have a custom ROM, eg. Pixel Experience installed?
There are some ROMs around at the moment that have a broken implementation of the audio-driver.
Android-devices MUST only play the audio locally _or_ remote via AirAudio, this is defined by Google.
I think you have to wait for an update of your ROM or switch to another ROM like others did :-/
-------
Is this something that could possibly be taken into consideration for a future update as this means I cannot stream audio from all sources (e.g radio apps and Spotify)to any DLNA output.
I really like AOSP Extended and would rather not switch to a different ROM.
Many thanks,
herges
Click to expand...
Click to collapse
I only compile unofficial builds. You can try to contact AospExtended devs, but mind that Pie entered final state and they're focusing on Android 10 now. However if the problem can be fixed with some simple patch in sources and it wouldn't affect anything else in negative way, I am willing to apply it to my builds.
Mobile data is not turning off from QS. I have to click airplane to switch it off completely.
I dirty flashed this ROM over official build yesterday and everything was fine, but today I was just checking out LOS 17, and then decided to roll back to this ROM, so I clean flashed this ROM, but after clean flashing the mobile data wasn't turning on.
And my SD card wasn't getting detected either. It lead to a lot of mess because I was not able to flash the official build either which was also in the SD card, I can't connect my phone to computer either because the USB port of the phone is bit defected, when I did managed the SD card to get detected, the recovery wasn't installing the official build. I tried to install los17 again and it worked.
Right now I am using los 17 and I would really like to go back to aex pie (official or unofficial) can someone help?
Golbinex said:
I only compile unofficial builds. You can try to contact AospExtended devs, but mind that Pie entered final state and they're focusing on Android 10 now. However if the problem can be fixed with some simple patch in sources and it wouldn't affect anything else in negative way, I am willing to apply it to my builds.
Click to expand...
Click to collapse
Hi,
I went and installed the official ROM and there the audio routing using AirAudio works correctly so something must have got broken when you recompiled this using the latest security fixes.
mobihack said:
Mobile data is not turning off from QS. I have to click airplane to switch it off completely.
Click to expand...
Click to collapse
It works for me, make sure you don't have any app with root access, which can block it.
BlackWhale2108 said:
I dirty flashed this ROM over official build yesterday and everything was fine, but today I was just checking out LOS 17, and then decided to roll back to this ROM, so I clean flashed this ROM, but after clean flashing the mobile data wasn't turning on.
And my SD card wasn't getting detected either. It lead to a lot of mess because I was not able to flash the official build either which was also in the SD card, I can't connect my phone to computer either because the USB port of the phone is bit defected, when I did managed the SD card to get detected, the recovery wasn't installing the official build. I tried to install los17 again and it worked.
Right now I am using los 17 and I would really like to go back to aex pie (official or unofficial) can someone help?
Click to expand...
Click to collapse
I think you broke your firmware partition so network drivers (wifi, mobile data) don't work. Try to flash official xiaomi firmware (not ROM). https://forum.xda-developers.com/re...lopment/firmware-xiaomi-redmi-note-4-t3760917
herges said:
Hi,
I went and installed the official ROM and there the audio routing using AirAudio works correctly so something must have got broken when you recompiled this using the latest security fixes.
Click to expand...
Click to collapse
This ROM is different than official one, because it has different device sources, the issue is caused by dotOS device sources. You can try to contact devs of some ROM where AirAudio works and ask them how they fixed it or use official one.
Golbinex said:
I think you broke your firmware partition so network drivers (wifi, mobile data) don't work. Try to flash official xiaomi firmware (not ROM). https://forum.xda-developers.com/re...lopment/firmware-xiaomi-redmi-note-4-t3760917
Click to expand...
Click to collapse
I think firmware does not get affected when ROM is changed/messed with, also the mobile data was working when I was using the los 17 (which I flashed after this rom wasn't turning on the mobile data).
I did a lot of things that I don't remember now (rebooting into recovery couple of times helped with the sd card detection issue), but in the end I was able to clean flash the official build with opengapps.
I can't be sure but I think bitGapps is responsible for this mess, which I used with LOS 17.
The order of ROMs on my phone from yesterday is aex official (everything fine)> aex unofficial (fine)> los 17 (I think the problem started here when I flashed bitGapps)> aex unofficial (no mobile data)> los 17 (mobile data works)> aex official (everything fine).
Thanks anyway for your help.
mobihack said:
Mobile data is not turning off from QS. I have to click airplane to switch it off completely.
Click to expand...
Click to collapse
For me, mobile data is not turning on
---------- Post added at 10:46 PM ---------- Previous post was at 10:30 PM ----------
BlackWhale2108 said:
I think firmware does not get affected when ROM is changed/messed with, also the mobile data was working when I was using the los 17 (which I flashed after this rom wasn't turning on the mobile data).
I did a lot of things that I don't remember now (rebooting into recovery couple of times helped with the sd card detection issue), but in the end I was able to clean flash the official build with opengapps.
I can't be sure but I think bitGapps is responsible for this mess, which I used with LOS 17.
The order of ROMs on my phone from yesterday is aex official (everything fine)> aex unofficial (fine)> los 17 (I think the problem started here when I flashed bitGapps)> aex unofficial (no mobile data)> los 17 (mobile data works)> aex official (everything fine).
Thanks anyway for your help.
Click to expand...
Click to collapse
Mobile data does not work only with this rom.
Flashed Pixel Experience and mobile data worked. Flashed AEX unofficial again and it doesn't.