This is Android 4.4.4 kitkat compiled from scratch from some other device sources that you find on the web. Adapted to fairphone FP1(U).
It includes various security fixes on top of 4.4.4 - but most likely not all. Major security hole detectors are green now (VTS, Bluebox, Zimperium).
NOTE: PHONES CAN BE LIFE SAVERS. DON'T RELY ON THIS PHONE AS YOUR SOLE COMMUNICATION MEANS. I HAVE NOT TESTED EMERGENCY CALLS, NOR CAN I GUARANTEE THAT THIS PHONE WILL WORK IF YOU ARE IN DANGER. CARRY ANOTHER PHONE WITH YOU. DON'T GO FOR A 3 DAY HIKE ONLY WITH THIS PHONE!
Without much ado...
To install...
- Flash the recovery from here: https://basketbuild.com/filedl/devs?dev=chrmhoffmann&dl=chrmhoffmann/fp1-kk-stock/recovery.img
- Boot into recovery and flash the rom, eg. with adb sideload. Download here: https://basketbuild.com/filedl/devs...mhoffmann/fp1-kk-stock/fp1-kk444-CH-0.9.7.zip MD5sum: 9140c93ff8f2b8327fdd330d2448c16f
- I guess you also want to flash some KK gapps that can be found somewhere (e.g http://opengapps.org/?api=4.4&variant=nano)
- You might also lose your IMEI like me? Don't PANIC! The IMEI's are noted on your FP. Remove the battery and write down the numbers. Then once you have booted the phone, follow this simple tutorial to fix this: https://www.facebook.com/fXDAdev/posts/448292925303711
Bugs:
- IMEI loss when flashing from stock FP1. No clue why this happens. Are we somehow overriding some NVRAM?
- CTS is complaining about some issues. https://christianhoffmann.info/2015.11.29_16.17.03/testResult.xml
- As this is a merge of 4.4.4 into the MTK stuff, watch out for more bugs than the previous release. Not merged: the new 4.4.4 dialer screen (we stick with 4.4.2 dialer as the modifications are too heavy), chromium does not support wml anymore (who cares?).
- You most likely need to wipe to install this when coming from the previous KK version to 4.4.4. Email app e.g. seems to crash without.
- Playstore version of Google Authenticator does not work (see https://github.com/google/google-authenticator-android/pull/4). Use the OSS version https://github.com/google/google-authenticator-android/releases - this is not specific to FP1 but seems an MTK issue.
- A dirty update (without wipe) from 0.8 on an encrypted device seems to reboot once during the "Android is upgrading" dialog
- Sometimes the lower part of the homescreen launcher seems to lose transparency.
Changelog fp1-kk444-CH-0.9.7 (you might want to check if there are new gapps here as you need to flash them again at same time: http://opengapps.org/):
- Android Security Updates from Google bulletin 1-MAY-2016 (https://source.android.com/security/bulletin/2016-05-01.html)
- Kernel CVEs including the mediatek wifi ones from https://source.android.com/security/advisory/2016-03-18.html, CVE-2016-2549, CVE-2016-2847, CVE-2016-2547, CVE-2016-2546, CVE-2016-2545, CVE-2016-2384
Changelog fp1-kk444-CH-0.9.6 (you might want to check if there are new gapps here as you need to flash them again at same time: http://opengapps.org/):
- Android Security Updates from Google bulletin 2-APR-2016 (https://source.android.com/security/bulletin/2016-04-02.html)
- Kernel CVEs including the one from https://source.android.com/security/advisory/2016-03-18.html, CVE-2015-7550, CVE-2016-0774, CVE-2016-0821, CVE-2016-0723.
Changelog fp1-kk444-CH-0.9.5 (you might want to check if there are new gapps here as you need to flash them again at same time: http://opengapps.org/):
- Android Security Updates from Google bulletin 1-MAR-2016 (https://source.android.com/security/bulletin/2016-03-01.html)
(incl. the kernel fixes that Google only publishes for Google One / Sprout - ported to MT6589)
Changelog fp1-kk444-CH-0.9.4 (you might want to check if there are new gapps here as you need to flash them again at same time: http://opengapps.org/):
- Android Security Updates from Google bulletin 1-FEB-2016 (http://source.android.com/security/b...016-02-01.html)
- Kernel CVE CVE-2015-8785
Changelog fp1-kk444-CH-0.9.3:
- Android Security Updates from Google bulletin 1-JAN-2015 (http://source.android.com/security/bulletin/2016-01-01.html)
- Some kernel CVEs (CVE2015-8543, CVE2015-8575, CVE2015-7509)
- Attempt to fix German's E-PLUS on O2 roaming
Changelog fp1-kk444-CH-0.9.2:
- Fix that you can now call funny numbers like *143# without phone application crash
- Fix to be able to add contacts to SIM card
Changelog fp1-kk444-CH-0.9.1:
- several kernel CVEs (CVE-2015-5697, CVE-2015-8539, CVE-2015-8215, and a few more without CVE yet)
- the december 1st security advisory bulletin skia issue introduced in 0.9.0 - aka as the dilbert bug - is fixed now
Changelog fp1-kk444-CH-0.9:
- android security bulletin https://source.android.com/security/bulletin/2015-12-01.html
- also update gapps if you install them: http://opengapps.org/?api=4.4&variant=nano
Changelog fp1-kk444-CH-0.8:
- google location providers are used now, which should enable network location provider (in case you installed google apps).
Changelog fp1-kk444-CH-0.7:
- National roaming should be fixed (at least as good as CM). If you still have issue with national roaming, send me your mmc/mmn data.
- Use original FP1 lens parameters for fm50af lens - does this improve the auto/manual focus issues that some people reported compared to stock FP jellybean?
- Attempt to fix the problem where sometimes the scrollbar and recents screen stopped working and screen locked despite having higher screen timeouts.
- Full CTS result: https://christianhoffmann.info/2015.11.29_16.17.03/testResult.xml
Changelog fp1-kk444-CH-0.5:
- SELinux enforcing
- Camera app now shows all resolutions
- adb now requires acceptance of adb key
Changelog fp1-kk444-CH-0.4:
- ro.adb.secure set
- browser default pages revisited (removed wrong thumbnail).
- removed MTK root CAs that are not in AOSP
- fixed remaining security false-positives in VTS and Bluebox Trustable - all green now
- USB default setting should be MTP now
Changelog fp1-kk444-CH-0.3:
- More CVE fixes (e.g CVE-2015-3845). VTS and Bluebox Trustable are almost green. For some reasons they still think "Stagefright" is not fixed. Zimperium nevertheless shows all stagefright OK. Edit: found out why. It's false positive as MTK reports errors in MPEG4Extractor differently than stock.
Changelog fp1-kk444-CH-0.2:
- Netflix issue fixed with new blob from E3
- Some CTS issues fixed
- More security fixes CVE-2014-7911
Changelog fp1-kk444-CH-0.1:
- Upgraded to 4.4.4_r2.0.1: Yay! That was an insane amount of work. The following "shortcuts" were taken:
-- Chromium sources taken from AOSP - MTK added wml but it was too much work to merge this back in
-- Email app sources taken from aosp - MTK customized something there esp. exchange sync, is that really giving someone problems?
-- Dialer app taken from MTK without 4.4.4 updates - that stuff is too heavily customized also for dual sim, and 4.4.4 revamped the UI, so this was just too much work for now.
- Latest security fixes up to November 2015. Security fixes also for wpa_supplicant_8 (thanks to Michael Bestas for collecting them for CM)
- Kernel sec fixes
- FP1 power profile xml (does this actually change anything)
As usual some credits:
- @Santhosh M : for some advice on the modem/baseband
- @keesj and fairphone for ___providing___ me a fairphone that replaced my own broken one (never figured out why it doesn't boot anymore)
- @CyanogenMod and koush for superuser stuff that I kanged into the MTK stock
- @CyanogenMod for the stagefright fixes
Let me know if
- it works also on older FP1 (without U).
- you have problems with your IMEI, too
- if you find other major issues
- if you think I am missing some security updates
- i had some issues getting the "phone" part of it work. Somehow it started working - not sure what it was. If you don't get the phone (call, etc.) to work, check your IMEIs first.
Reserved - why do all people do this?
chrmhoffmann said:
This is Android 4.4.2 kitkat compiled from scratch from some other device sources that you find on the web. Adapted to fairphone FP1(U).
It includes various security fixes on top of 4.4.2 - but most likely not all.
NOTE: PHONES CAN BE LIFE SAVERS. DON'T RELY ON THIS PHONE AS YOUR SOLE COMMUNICATION MEANS. I HAVE NOT TESTED EMERGENCY CALLS, NOR CAN I GUARANTEE THAT THIS PHONE WILL WORK IF YOU ARE IN DANGER. CARRY ANOTHER PHONE WITH YOU. DON'T GO FOR A 3 DAY HIKE ONLY WITH THIS PHONE!
Without much ado...
To install...
- Flash the recovery from here: https://basketbuild.com/filedl/devs?dev=chrmhoffmann&dl=chrmhoffmann/fp1-kk-stock/recovery.img
- Boot into recovery and flash the rom, eg. with adb sideload. Download here: https://basketbuild.com/devs/chrmhoffmann/fp1-kk-stock
- I guess you also want to flash some KK gapps that can be found somewhere (e.g http://opengapps.org/?api=4.4&variant=nano)
- You might also lose your IMEI like me? Don't PANIC! The IMEI's are noted on your FP. Remove the battery and write down the numbers. Then once you have booted the phone, follow this simple tutorial to fix this: https://www.facebook.com/fXDAdev/posts/448292925303711
Bugs:
- IMEI loss when flashing from stock FP1. No clue why this happens. Are we somehow overriding some NVRAM?
As usual some credits:
- @Santhosh M : for some advice on the modem/baseband
- @keesj and fairphone for ___providing___ me a fairphone that replaced my own broken one (never figured out why it doesn't boot anymore)
- @CyanogenMod and koush for superuser stuff that I kanged into the MTK stock
- @CyanogenMod for the stagefright fixes
Let me know if
- it works also on older FP1 (without U).
- you have problems with your IMEI, too
- if you find other major issues
- if you think I am missing some security updates
- i had some issues getting the "phone" part of it work. Somehow it started working - not sure what it was. If you don't get the phone (call, etc.) to work, check your IMEIs first.
Click to expand...
Click to collapse
so far it works on my fp1 (without U), no Problems with my IMEI-Numbers. Thank you very very much, great!
Just flashed it and it works! Thank you so much! (although instructions how to create such a rom would be nice for me )
EDIT: some answers to your question:
I am using the FP1u.
No problems with my IMEI.
Other major issues: none noticed, and this actually fixed the transparency bug in the Play Store
Missing security patches: Stagefright CVE-2015-6602 is not fixed.
Thank you very much!
How do i flash the recovery? the typicall fastboot method does not work for me (says "flash not supported")
fredflegel said:
How do i flash the recovery? the typicall fastboot method does not work for me (says "flash not supported")
Click to expand...
Click to collapse
There's an old thread about it: http://forum.xda-developers.com/showthread.php?t=2615613
So in this case:
Code:
adb push recovery.img /sdcard/
adb shell
su
dd if=/sdcard/recovery.img of=/dev/recovery
And because I can never remember if it's volume up or down when powering on: "Hold the Volume Up button, while at the same time press and hold the Power button. Hold these two buttons at the same time for about 10 seconds until the screen changes."
Then install from sideload, etc. and
Code:
adb sideload fp1-kk-stock-0.1.zip
Takes quite a while to update. I did NOT disable rom recovery, I don't think this one reverts the recovery, right?
aaaand
Sound and bluetooth seem to work fine, didn't test more so far.
Edit: By the way, are you going to do a Lollipop rom? That would be even more awesome than this. Meanwhile: Good job for raising the FP1 software to the minimum requirements for today.
Great Work! Thanks alot!
I will check this rom thoroughly. On little cosmetic issue that was fixed in Fairphones official rom is the issue with national roaming in german 02/E-Plus networks. I now allowed data roaming as a workaround, but this can get pretty expensive pretty soon. Any chance you can fix that in a future build?
fredflegel said:
Great Work! Thanks alot!
I will check this rom thoroughly. On little cosmetic issue that was fixed in Fairphones official rom is the issue with national roaming in german 02/E-Plus networks. I now allowed data roaming as a workaround, but this can get pretty expensive pretty soon. Any chance you can fix that in a future build?
Click to expand...
Click to collapse
You can enable "National data roaming" with GravityBox, which you can install via the Xposed installer. Helped in Austria with bob (and A1)
You forgot to mount the "external" storage:
Code:
tmpfs /storage/emulated tmpfs rw,seclabel,relatime,mode=755,uid=1023,gid=1023 0 0
Workaround for getting the correct one for now:
Code:
umount /storage/emulated
mount -t vfat /dev/block/mmcblk0p8 /storage/emulated
But there are still symlinks to /storage/emulated/legacy.
So that needs some kind of fix up.
ccxxx said:
You forgot to mount the "external" storage:
Code:
tmpfs /storage/emulated tmpfs rw,seclabel,relatime,mode=755,uid=1023,gid=1023 0 0
Workaround for getting the correct one for now:
Code:
umount /storage/emulated
mount -t vfat /dev/block/mmcblk0p8 /storage/emulated
But there are still symlinks to /storage/emulated/legacy.
So that needs some kind of fix up.
Click to expand...
Click to collapse
I think that you are using the old non-repartitioned fp1?
There's no such thing as /dev/block/mmcblk0p8 anymore on the repartitioned devices.
Chris
chrmhoffmann said:
I think that you are using the old non-repartitioned fp1?
There's no such thing as /dev/block/mmcblk0p8 anymore on the repartitioned devices.
Chris
Click to expand...
Click to collapse
Uhm, yes, I guess.
TIL https://fairphone.zendesk.com/hc/en-us/articles/201327645-What-is-Fairphone-s-storage-layout-
ccxxx said:
Uhm, yes, I guess.
TIL https://fairphone.zendesk.com/hc/en-us/articles/201327645-What-is-Fairphone-s-storage-layout-
Click to expand...
Click to collapse
You should then upgrade. It's much nicer with a single partition... And as you can see, I don't support the old storage layout any more
Chris
Upgrade to 4.4.4. available
See OP. Please test this. It's an update to android 4.4.4 and lots of additional security fixes.
Oh, and yeah, I recommend to wipe. Email (e.g. and maybe others) will crash without.
Chris
It wasn't obvious, how to do that, so I downloaded the "Storage Upgrader 1.8.7 * (~200MB)" from https://fairphone.zendesk.com/hc/en-us/articles/201189497-Fairphone-OS-multiple-versions-
It doesn't update the partitions when flashing, it does so on the first boot. It also overwrites the recovery.
After that I installed the 4.4.4 image and it boot loops: https://gist.github.com/ChristophHaag/64da8b31533d2c562c92
edit: And so does the 4.4.2 image that has worked before.
*sigh*
edit 2: Formatted a few partitions and tried again - now 4.4.4 works.
0.2 released.
It should fix Netflix (will confirm when all apps are installed after wipe) and should also squash a security problem that bluebox reported (CVE-2014-7911).
It should also make less CTS tests fails.
Still uploading... Edit: Uploaded.
Chris
Hallo, nach dem neuesten update funktioniert xposed-aktivierung nicht mehr. Sonst alles bestens
Sorry, in english:
After the newest update to 4.4.4 no chance to activate xposed-framework. Anyway, thanks a lot
for your hard work
btw Google Authenticator doesn't seem to work correctly on the 4.4.2 version. Authy works though.
jogri said:
Hallo, nach dem neuesten update funktioniert xposed-aktivierung nicht mehr. Sonst alles bestens
Sorry, in english:
After the newest update to 4.4.4 no chance to activate xposed-framework. Anyway, thanks a lot
for your hard work
Click to expand...
Click to collapse
Yes, the last security patches break xposed. https://android.googlesource.com/pl...+/d4d3181d013f8d9b96de8e396b029f8a418894a7^!/
See e.g. here: https://plus.google.com/114407246718577124209/posts/BwiPxSu84bD
Chris
z3ntu said:
btw Google Authenticator doesn't seem to work correctly on the 4.4.2 version. Authy works though.
Click to expand...
Click to collapse
This is most likely related to this issue: https://github.com/google/google-authenticator-android/pull/4
It is most likely an MTK issue with problematic math library (or something like that).
Anyway, it works for me when I use the open source version of the google authenticator: https://github.com/google/google-authenticator-android/releases
Chris
Jeah, I used the Play Store version, but this is also mentionable in "known bugs" (and that they should use the open-source version)
Related
FRX07.1 is here!!
This is a maintenance release - basically taking the newest components to make a completely up-to-date (as of Sept. 1).
Quite a lot has changed since FRX06 - the install process hasn't really, but be sure to read the changelog in the next post and the caveats in post #3!
<<<This is a link to the... FAQ Click it!!>>>
I have created a complete bundle of FroYo with a stable kernel from GIT (August 19 / 1348), and rootfs from GIT (Sept. 2).
Please, feel free to DONATE to the XDAndroid project!
Every little bit helps!
Directions:
1. Download the full bundle (zip). (Updated September 1 2011)
If instead you just want the system.ext2 (zip) (Updated July 15 2011) file by itself... Don't download this if you're not sure! Grab the full bundle!
2. Extract it. You’ll see a folder, FRX07.1, copy its contents to the root of your SD card. If you want to run Android from a folder instead of all the files on the root of the card, follow the steps below.
3. Go into the STARTUPS folder. Grab the appropriate startup.txt for your device (if you don't know what device you have, you should read the FAQ), and move it to the root of the card (or where you run haret.exe from. If you want to change the location of the build, put a rel_path= statement in the cmdline section of the startup.txt. Mine is located two folders deep on the SD, so my rel_path=Androids/TP2Ref)
4. Screen calibration - you have three choices:
Re-use an old ts-calibration file if you have it and you know it's good.
Download the ts-calibration.zip file and extract it to where you put the rest of the files (root of SD or in a folder - make sure it all stays together!)
Manually calibrate - boot with no ts-calibration file and watch the boot process - you'll be asked to hit 5 points to calibrate the screen. If you have issues calibrating, try an older kernel (1225 works well) Once you have the calibration file hold on to it (make 15 copies if it's a good one ), reboot & go back to the newest kernel!
6. Run haret.exe.. Profit!
Let it settle out on the first boot. Many have reported they had to reboot basically because it was so slow - if you let it sit for about 10 mins so the media scanner can go thru everything, etc. it will be much more pleasurable experience. If you want adb in and watch the processes via top, you'll see why the phone seems so slow - there's lots of background processes cranking because this is the first boot .
Troubleshooting:
Please read the... FAQ
If you have any issues with the kernel, feel free to change it:
There are some devices that are having issues with the newest kernels. Please see the kernel autobuild service to get archived kernels. Once you download a replacement kernel, go to where you run haret.exe from - remove your old zImage/modules-xxxxx.tar.gz. Take the new zImage/modules-xxxxx.tar.gz and replace the old ones, same folder - where you run haret.exe from. Make sure the ‘zImage’ is named just that. Do not rename the modules file, do not extract it - should be in .tar.gz format.
See Incremental Updates for more information on updating the kernel and other components.
Random issues can often be solved by forcing the system to create a new data.img. If you're worried about losing data (all user data is stored in the data.img!!), Titanium Backup works quite well. If you wish, you can rename the data.img to something else, and let the system create a new one - just to see if it resolves your problem.
Similarly, if you wish try formatting your SD card - I prefer to use the HP Tool - do a full format, FAT32.
Even though this build is considered fairly stable, you are more than likely going to run into issues. The next post will address issues particular to this build - PLEASE READ THESE before asking questions! Feel free to post questions in this thread, I will do my best to address them. Big thanks to stinebd for releasing the system image, and of course the other developers for their hard work on making these kernels available.
stinebd's Changelog:
stinebd said:
Here’s a new release for you, folks. This is a major release with a ton of changes, new features, and fixes. Our friend hyc/highlandsun did most of the heavy lifting for this release. Highlights include a rewritten RIL with support for world phones and greatly improved CDMA support; fixes for the media codecs; fixes for MMS on Sprint; increased security with the Superuser app.
A list of changes is included below. The FRX07 system image is available for download now, and will require the use of a new rootfs image, also available now. Additionally, we have a new bundle containing everything needed to enjoy a full FRX07 system.
Note: Due to the incredibly long list of changes, this is a somewhat condensed, terse changelog describing only the overall scope of the changes.
FRX07:
frameworks/base:
Major frameworks changes for CDMA/GSM dual-mode worldphone support. (hyc)
Fixes for data connection handling to improve startup time. (hyc)
Fixes for wifi handling to avoid issues on hanged drivers. (hyc)
Stagefreight (media codecs) fixes. (hyc/viruscrazy)
Fixes for Sprint’s wonky MMS markup structure. (hyc)
Fix MediaScanner not finding audio files (including ringtones) in system.ext2
hardware/libhardware_legacy:
Minor GPS driver fixes. (Alex[sp3dev])
Rename wifi interfaces to wlan0 on all devices (hyc)
hardware/xdandroid-ril: Major RIL refactoring for improved performance on all devices, and added CDMA/GSM dual-mode worldphone support. (hyc)
packages/apps/Gallery3D: Switched back to Gallery3D as the gallery app (closes bug #111)
packages/apps/Mms: Fixes for Sprint’s wonky MMS markup structure. (hyc)
packages/apps/Phone: Fixes for CDMA/GSM dual-mode worldphone support. (hyc)
packages/apps/Superuser: Added the Superuser package for authorizing su privileges. This, along with our signed builds, provides greatly increased security for the end user (mostly against malicious apps from the Market).
system/extras/su: Added as a dependency for the Superuser package
vendor/qcom/android-open: Include missing stagefright codec symbols. (hyc/viruscrazy)
To coincide with the FRX07 system image, the following rootfs changes have been made:
init.froyo.rc modifications...
Adjust wpa_supplicant service for the new abstraction provided by libhardware_legacy, as well as interface rename
Abstract the hciattach service to provide bluetooth support on both chipsets
Rename wifi interface to wlan0 on all devices
apns-conf.xml updated
keymaps completely reorganized, and RHOD end-call key has been remapped to be the Home key in Android.
default.prop: set ro.secure=1 to lock down the adb shell - su can be used with the Superuser app to authorize root access in adb if needed.
Click to expand...
Click to collapse
Layman's Changelog
(As in, the changelog I wrote )
FRX07.1 Changelog:
RHOD - all buttons on the front no longer wake the device. Only the power button wakes the device now.
Updated to the newest RIL
hyc's modified libs for video now baked in - *most* HQ YouTube videos (and other HQ videos) should finally work!
RHOD & TOPA - Userland (Android) now controls the LED by default now. If you need to debug sleep, you will have to change the behavior manually.
Facebook sync should now work, out-of-box.
FRX07 Changelog:
Updated RIL (thanks hyc!) - this covers many different bugs that were in the old RIL - I'm only going to cover the major ones...
CDMA now works correctly (for the most part). force_cdma (and north_am_dialing) is now deprecated (not needed/ignored!)
You can boot with a SIM in on a CDMA device and choose your GSM or CDMA on the fly under Settings.
Location based on towers now works on CDMA.
1xRTT now displays correctly, but I never seem to get EVDO Rev.a... I always get 0. This is represented by a 3g icon, as this is what the Android framework provides.
Full MMS support! Please see this page for configuration instructions. Will need help fleshing out the list of carriers folks!
Spotty service, switching towers, etc should no longer cause the dreaded SoD (Sleep of Death) condition!
(Basic audio) 3.5mm support for RHOD400/500
Droidwall works out of the box now
Keyboard backlight now fades in/out
Gallery3D back in! Picasa Web Sync comes with it
A couple new apps added to AndroidApps folder:
rpierce99's app GetLogs
Titanium Backup
Caveats:
BT - works! But audio doesn't route. See this thread if you're feeling adventurous and want to play with/don't mind using some unstable/incomplete code...
That audio routing thread is in the RHOD section, and I've only tested it on a RHOD - but AFAIK it should work on other devices. Let me know.
I just trying it....after 1 hours in initial boot proses my battre was drain..and until now i never pass the initial boot
I think FRX06 best for my RAPH100 , but it can frezze if i put sim card..any idea to add my APNs mobile Network manually on FRX06?but i don't know how to do it?
Initial boot (no SIM)
Very nice! Just upgraded/updated new data.img to include grabbing the new kernel package (1340), rootfs and system files! I haven't tried anything that accesses data yet (ran it with no SIM) but FRX07 seems very stable on the RAPH100. However, it took a tad longer than what I'm used to on initial boot. Going to format and try with no androidapps folder and no media folder and see if that's what cuts down the initial boot. All in all awesome job... but something tells me you already knew that...
R^7Z said:
Very nice! Just upgraded/updated new data.img to include grabbing the new kernel package (1340), rootfs and system files! I haven't tried anything that accesses data yet (ran it with no SIM) but FRX07 seems very stable on the RAPH100. However, it took a tad longer than what I'm used to on initial boot. Going to format and try with no androidapps folder and no media folder and see if that's what cuts down the initial boot. All in all awesome job... but something tells me you already knew that...
Click to expand...
Click to collapse
nice report..but i wanna know if you boot with SIM card..it's freeze your device?
If it freezed with FRX06 it shouldn't freeze anymore,hyc/highlandsun's ril solved it..
it very stable, but maybe someone tried install a new Market app?
GoldAngelo said:
it very stable, but maybe someone tried install a new Market app?
Click to expand...
Click to collapse
I haven't, give it a shot - I asked the same thing before release .
system doesn't detect my SIM, it said "No service" despite my SIM operated normally in WinMo
datbi_201 said:
system doesn't detect my SIM, it said "No service" despite my SIM operated normally in WinMo
Click to expand...
Click to collapse
What phone? Have you set the phone to be on GSM mode in Android...?
arrrghhh said:
What phone? Have you set the phone to be on GSM mode in Android...?
Click to expand...
Click to collapse
i'm using Ral, i installed FRX06 last week and everything was ok w/o any setting. But now with FRX07 ...
i re-run Haret from WinMo but it hang up with command "(something): read retry", so i thought that my SDcard maybe corrupt. Just re-formated and re-run Haret.
it stopped/paused too long with command: "htc_cable_notify_do_work: 0"
and now, it's hanging up completely with "r5:00000000 r4:00000000"
what'd i do
tks
Please try what was asked in the previous post and report your findings. The change logs in the first few posts make mention of a framework change. Meaning FRX07 might require some additional setting changes, depending on your phone/device...
By the way, what's a Ral? I have a RAPH100 and a RAPH110, which one do you have?
Well done with this build! It seems that the WiFi Turn Off- Turn On - Doesn't work anymore bug is gone (for my RAPH100).
LE: And it seems that the clock network sync bug is gone, too.
R^7Z said:
Please try what was asked in the previous post and report your findings. The change logs in the first few posts make mention of a framework change. Meaning FRX07 might require some additional setting changes, depending on your phone/device...
By the way, what's a Ral? I have a RAPH100 and a RAPH110, which one do you have?
Click to expand...
Click to collapse
i have Raph100 and i followed all steps carefully but install progress still hang up
First of all, great work on this guys! I've been waiting for quite a while and this release works great on my RHOD400.
Onto my feedback for the RAPH800...
I can't boot the kernel that's bundled with the 7/16 release.
It boots with endless repeat of "OOPS - smd_tty buffer mismatch"
I went back through a few kernels from the build page. Each of the following builds boot with the same error
htc-msm-linux @ 20110716_005117
htc-msm-linux @ 20110711_082424
htc-msm-linux @ 20110627_223755
When I got to this build:
htc-msm-linux @ 20110622_180615
The boot froze for a while (~30 minutes) and I finally reset the device. It booted fine after the reboot.
I'm not sure if this information helps at all, but I hope it helps in pinpointing a problem what changed over this range of builds.
Again, thanks so much. I'm looking forward to testing FRX07! I'm thinking I'll be able to use it daily on my RHOD!
Superuser permissions, heck yeah! That's been one of the more annoying things about xdandroid; some apps just don't like how it does root, which I suspect might have something to do with the lack of the aforementioned app. Plus, it's just not safe having su be autoconfirmed. I appreciate it.
Can fellow Raph100 owners verify if the physical keyboard lights are always on in closed position? When drawn, the lights goes off which is the reverse of how it should function. The LCD panel doesn't turn off fully as well, it's lit slightly.
Otherwise, it's a good stable build. No SOD's yet with the stock kernel. The device is not warm on standby as well compared to the previous build installed. DroidWall works out of the box without the usual tweak as well.
Thanks & kudos!
agibby5 said:
First of all, great work on this guys! I've been waiting for quite a while and this release works great on my RHOD400.
Onto my feedback for the RAPH800...
I can't boot the kernel that's bundled with the 7/16 release.
It boots with endless repeat of "OOPS - smd_tty buffer mismatch"
I went back through a few kernels from the build page. Each of the following builds boot with the same error
htc-msm-linux @ 20110716_005117
htc-msm-linux @ 20110711_082424
htc-msm-linux @ 20110627_223755
When I got to this build:
htc-msm-linux @ 20110622_180615
The boot froze for a while (~30 minutes) and I finally reset the device. It booted fine after the reboot.
I'm not sure if this information helps at all, but I hope it helps in pinpointing a problem what changed over this range of builds.
Again, thanks so much. I'm looking forward to testing FRX07! I'm thinking I'll be able to use it daily on my RHOD!
Click to expand...
Click to collapse
I can't get my RAPH800 to boot at all! Might be a deeper issue with the device tho. Your info does help, I needed someone to narrow down when the issue first started. Thanks!
About OmniROM
The goal of Omni is to experiment with Android development because we enjoy it. Omni isn’t better, just different. It’s another option for the billion Android users out there. Android (vs. iOS and every other mobile OS) has thrived on options as well as the gigantic, talented development community that has emerged to build those options. That’s the beauty of Android – that you can pick and choose from a smorgasbord of devices with varying features and functionality.
Omni is a chance to get involved, no matter who you are. Developers, whether you’ve been developing apps for a week, or ROM features for 3 years, you’re welcome. Users, we know you want to help out, and now you can – Omni actively encourages bug reports and feature requests, which can be added to our publicly accessible roadmap. What’s the point in giving you a ROM, and forcing you to not tell us about any bugs you find?
We also recognise how people use Custom ROMs – we’re all custom ROM users and developers ourselves – the argument that “nightlies are not for end users” is over-used, and no longer valid. We’ve found that the vast majority of users want to get nightly updates to their ROM. For that reason, nightlies aren’t a playground – nightlies are for new features that are finished. You should be able to expect the same stability and reliability from a nightly as you would from a “release” ROM, and can report any bugs that prevent this from happening.
We know not everyone wants to update their ROM daily, and you are free to update as frequently or infrequently as you like. Omni is about flexibility and giving users what they expect – and we are excited to see where the community goes with it.
Click to expand...
Click to collapse
Info from omnirom http://omnirom.org/general/android-l-omnirom-progressing/
Disclaimer
Standard disclaimer applies, your warranty is void, this may eat your dog or burn your house down, delete all your pictures, etc.
This is an early stage release so many things are broken since many patches and fixes haven't been imported from old branches yet.
How to install:
Reboot to recovey
A backup is Recommended, you're gonna loose all your data
Wipe data
Flash rom
Flash SuperSU 2.19 2.40 or up just after the rom
http://download.chainfire.eu/supersu -> This is IMPORTANT
Flash Netflix fix if you need it -> Download
Reboot
Around 5 minutes are required for the first boot
Reboot again to recovery
Flash Gapps (See below)
How to update from a previous version:
Reboot to recovey
Flash rom
Flash SuperSU 2.40 or up just after the rom http://download.chainfire.eu/supersu -> This is IMPORTANT (not needed anymore)
Flash Netflix fix if you need it -> Download
Reboot
Gapps download:
Check http://forum.xda-developers.com/android/software/gapps-consolidated-gapps-thread-t3064693
How to report a bug
Use the search function, if the bug has already been reported and I or another person has answered do NOT report it again. I'm tired of writing ten times the same thing.
A bug report function is embedded in XDA forum look at the top there's a section called "Bug Reports". Use it
Provide a logcat and/or dmesg. Search on XDA if you don't know how to get a proper log
Always provide which model you are using and other information that you think could be useful to solve the bug
Downloads:
This is an early preview with lots of bugs and not usable as a daily driver. You have been warned. Flash this only if you are sure about what are you doing.
Download folder: https://www.androidfilehost.com/?w=files&flid=21696
Starting from 20150506 I'm uploading automated builds: this means that they should be treated as nigthlies (I won't create a new one every 24 hours though). All the new files will be placed in the "Download folder" automatically, so, if no new changes from my part, I will NOT update the changelog. These builds will include all the updates and commits from official Omnirom repos plus my commits not yet merged for our tablets. Good luck
Commits: -> Updated to 5.1.1_r2
Necessary commits
In frameworks_native: https://gerrit.omnirom.org/#/c/13068/ and https://gerrit.omnirom.org/#/c/13069/
In frameworks_av: https://gerrit.omnirom.org/#/c/12528/, https://gerrit.omnirom.org/#/c/12529/ and https://gerrit.omnirom.org/#/c/12530/ (in this order)
In kernel_samsung_smdk4412: https://gerrit.omnirom.org/#/c/12223/ (SELINUX to permissive) , https://gerrit.omnirom.org/#/c/13055/ (Kernel compression)
Optional commits:
Enable Stylus pointer toggle: https://gerrit.omnirom.org/#/c/13606/, https://gerrit.omnirom.org/#/c/13650/, https://gerrit.omnirom.org/#/c/13651/
And finally, if you want to test and/or help:
Netflix experimental codecs fix: https://gerrit.omnirom.org/#/c/13716/
Other commits not made by me:
Nothing here as of now
If you wish to have a kernel with overclock and other features, you can find the kernel sources for my custom kernel "mm_alpha" at https://github.com/marco9333/android_kernel_samsung_smdk4412 . See branch mm_alpha_lollipop for the working and updated version working with this rom (and other lollipop roms). I can share a compiled version, PM me if interested
Screenshots -> Click here
Donations:
Many thanks to Heide Ruehle and @Rand_
Thanks to:
Omnirom core devs
@iofthestorm(ported omnirom 4.4 and made it official for our devices)
@humberos (various patches and asked for an official new android-5.0 branch)
@lirokoa (for his advices on wifi and camera hal)
I forgot someone ???
XDA:DevDB Information
OmniROM, ROM for the Samsung Galaxy Note 10.1
Contributors
marco9333
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: Testing
Created 2014-11-23
Last Updated 2016-11-13
Status of things:
Broken:
Charging off mode isn't working
Using torch tile causes a forced reboot, use torch app instead
Wi-fi tethering isn't working
Screen recording causes an hard reboot (Now it just does nothing or System UI crashes and restart)
I haven't tested other things yet....
Report if you found something new to add here
Notes:
Using a proxy in APN settings doesn't work. Thanks to @farinjini for pointing this out -> I don't know if this is working now or not
Changelog:
Older versions changelog
20141123
Initial release
20141125
Fixed stylus (S-PEN input)
Fixed graphical glitches in screenshots and while rotating screen Thanks to @lirokoa
Upstream changes -> updated to android release LRX21V and other "under the hood" changes
20141126 for N801x
Solved bootloop problem, I hope (not booting kernel)
20141130 for N8000
Partially working RIL (this has been really hard )
20141204-05
Upstream changes -> updated to android 5.0.1 LRX22C
Gps fixed. Thanks to @humberos
Added Performance control and Advanced in settings as in omnirom 4.4.4 (thanks to omnirom core devs)
Mobile partially fixed (need to run a script to make it completely work) (only N8000)
20141207 for N8000
Mobile data completely fixed
20141218
Upstream changes
Added advanced reboot (normal reboot, reboot to recovery and reboot to bootloader)
Fixed the problem with keyboard (need to disable physical keyboard from settings)
Fixed forced reboots caused by Youtube and G+
Minor fixes about technical things
20150108
Switched to android 5.0.2_r1 LRX22G
Upstream changes
Random reboots should be fixed -> see https://gerrit.omnirom.org/#/c/11024/ and https://gerrit.omnirom.org/#/c/10997/
20150206
Upstream changes -> See https://gerrit.omnirom.org/
Lots of code cleaning -> Better stability (I hope)
20150326/27
Switched to android 5.1 LMY47D
Upstream changes
20150401
Upstream changes
Switched to android 5.1_r3 LMY47I
Youtube, G+, firefox, etc. reboot fixed (experimental fix please report if problems)
20150407
Upstream changes
Netflix fix (experimental.. please report)
Properly "keyboard not showing" fix
20150506
Upstream changes
Android 5.1.1 LMY47V
New DRM vendor libs (Report if they "work miracles" with netflix)
20150510
Upstream changes
Pointer disabled by default when using S-Pen (Can be re-enabled in Settings see screenshot at #372)
Reintroduced keyboard fix (sorry about that)
20150519
Upstream changes
Android 5.1.1_r2 LMY47X
Netflix codec fix -> See https://gerrit.omnirom.org/#/c/13716/
20150628
Upstream changes
Android 5.1.1_r5 LYZ28E
20150928 or 20150927
Upstream changes
Android LYZ28J
Stagefright fixes
20151104
Upstream changes
Video playing fixed (Sorry guys and girls )
Chrome is now working
You need to enable the showing of keyboard after first boot: go to settings, language and input, current keyboard and enable Hardware(Show input method)
20161110
Untested build
Upstream changes
Android LYZ28N
Reserved
Workarounds and advices
Smoothness: Go to settings, about tablet and press repentantly Build_number until it gives you that you're now a developer, Go back, press on Developer options, scroll down and set Window animation scale, Transition scale and Animator scale to .5x
Toggle stylus (S-pen) arrow pointer:
Go to Settings, Language & input, put a tick or not on "show icon when using stylus" option
marco9333 said:
Status of things:
Working:
Boot
Bluetooth (switching on and scanning)
Rotation
Suspend/Resume (need to keep wifi on though)
Audio
Root (flashing SuperSU from recovery)
Gapps install and start (I've tried CM Gapps but login in is impossible)
Vibration
Hd videoplayback (tested youtube)
I forgot something ???
Partially working:
Screen -> Rotation causes graphics glitches
Video playbackaudio is working, decoders too but black video
Wifi (something wrong with this module, suspending the device with wifi off causes an hot reboot)
Broken:
RIL (phone calls, 3g and so on) for n8000 -> I'll try lirokoa advice -> need to import samsungRIL from android-4.4 tree
Camera (videos) -> Imported opensource camera hal -> taking pictures is fine but video are completely broken
Gps ->I 've waited enough and no position found -> some error regarding this in the logcat
I haven't tested other things yet....
Click to expand...
Click to collapse
Hey marco,
For graphics glitch when rotating you need:
https://github.com/CyanogenMod/andr...mmit/540345f70db4f0cea6ad3f1150d2cb2fac18da25
https://github.com/CyanogenMod/andr...mmit/4e7f61fd6a36345e7994c236d1c128c4c8a6a0ea
https://github.com/CyanogenMod/andr...mmit/db4cec0e189b84e5999ae5b3bef0e7a6c2bb3087
you can probably find those in 4.4 omnirom branch as well.
Then it should be fixed
lirokoa said:
Hey marco,
For graphics glitch when rotating you need:
https://github.com/CyanogenMod/andr...mmit/540345f70db4f0cea6ad3f1150d2cb2fac18da25
https://github.com/CyanogenMod/andr...mmit/4e7f61fd6a36345e7994c236d1c128c4c8a6a0ea
https://github.com/CyanogenMod/andr...mmit/db4cec0e189b84e5999ae5b3bef0e7a6c2bb3087
you can probably find those in 4.4 omnirom branch as well.
Then it should be fixed
Click to expand...
Click to collapse
Thanks I've already merged one of them yesterday (the first), and I need to check the second one. I don't know about the last one because I haven't found any settings in the various configs that enable BOARD_USE_MHEAP_SCREENSHOT. I need to check better though.
marco9333 said:
Thanks I've already merged one of them yesterday (the first), and I need to check the second one. I don't know about the last one because I haven't found any settings in the various configs that enable BOARD_USE_MHEAP_SCREENSHOT. I need to check better though.
Click to expand...
Click to collapse
Yes maybe the one for heap screenshot is not needed.
Sent from my Nexus 4 using XDA Free mobile app
i'll try and see if YT even works
Running N8010 device with N8000 BL
seems imposible to get it to work :silly:
LastStandingDroid said:
i'll try and see if YT even works
Running N8010 device with N8000 BL
seems imposible to get it to work :silly:
Click to expand...
Click to collapse
It's working I've just tested with a 720p video
marco9333 said:
It's working I've just tested with a 720p video
Click to expand...
Click to collapse
i'll see if it'll work for me i've never got it working with any build
LastStandingDroid said:
i'll see if it'll work for me i've never got it working with any build
Click to expand...
Click to collapse
I'm in the same boat as you, stuck with the leaked N8000 bootloader on my N8010, and youtube works great for me on last CM 11 build.
Nice work Marco!!
I've flashed your build (while building mine... ) and I've noticed that the keyboard doesn't show up, I had to go to Settings>Language & input>Current Keyboard and switch on the Hardware flag to make the keyboard appear.
Youtube works fine (audio and video)
I've played a couple of mp4 videos with a default gallery without a problem
Music plays fine with Apollo
It seem very good for such an early build...If only the log in with Google Account worked...:fingers-crossed:
Sooo nice rom only network works on N8000 and it will be my rom
- There is a problem with the default browser as it closes after opening on few seconds
- Graphics errors at multi tasks cards.
TheMorpheus said:
Nice work Marco!!
I've flashed your build (while building mine... ) and I've noticed that the keyboard doesn't show up, I had to go to Settings>Language & input>Current Keyboard and switch on the Hardware flag to make the keyboard appear.
Youtube works fine (audio and video)
I've played a couple of mp4 videos with a default gallery without a problem
Music plays fine with Apollo
It seem very good for such an early build...If only the log in with Google Account worked...:fingers-crossed:
Click to expand...
Click to collapse
I've tried CM gapps but it chrashes on login.... maybe some others google apps will work. I'll try to extract them from my nexus 5 official L rom.
mysarasaid said:
Sooo nice rom only network works on N8000 and it will be my rom
- There is a problem with the default browser as it closes after opening on few seconds
- Graphics errors at multi tasks cards.
Click to expand...
Click to collapse
I usually use chrome. Default browser should be "deprecated" and replaced by chrome. Graphical errors are still there (during switching off screen, rotation, taking screenshots and so on), lirokoa pointed some commits I'll try with them, but they should do the job. RIL is a priority for me too, but it's quite complex and the code changed a lot so I'll need some time to merge that part.
marco9333 said:
I've tried CM gapps but it chrashes on login.... maybe some others google apps will work. I'll try to extract them from my nexus 5 official L rom.
I usually use chrome. Default browser should be "deprecated" and replaced by chrome. Graphical errors are still there (during switching off screen, rotation, taking screenshots and so on), lirokoa pointed some commits I'll try with them, but they should do the job. RIL is a priority for me too, but it's quite complex and the code changed a lot so I'll need some time to merge that part.
Click to expand...
Click to collapse
For RIL, many things are needed and I can't test since I have N8013, but I can point you to some to a repo that might help you:
https://github.com/ArchiDroid/android_frameworks_opt_telephony/commits/cm-12.0
Looks to all SamsungExynos4RIL / Samsung STK commits. That should help.
lirokoa said:
For RIL, many things are needed and I can't test since I have N8013, but I can point you to some to a repo that might help you:
https://github.com/ArchiDroid/android_frameworks_opt_telephony/commits/cm-12.0
Looks to all SamsungExynos4RIL / Samsung STK commits. That should help.
Click to expand...
Click to collapse
I'll give it a try because when I tried to merge RIL from omnirom 4.4 I've got an enormous amount of conflicts. Thanks maybe them will speed up the fix
Sent from my Nexus 5 using XDA Free mobile app
I've tested latest Banks google apps for android L and they are working. This is the link http://fitsnugly.euroskank.com/?rom=banks&device=gapps (added in OP too)
marco9333 said:
I've tested latest Banks google apps for android L and they are working. This is the link http://fitsnugly.euroskank.com/?rom=banks&device=gapps (added in OP too)
Click to expand...
Click to collapse
it did remove my recovery after flashing this rom not sure why i was just unable to reboot to recovery (regular key combination)
used philz recovery rom worked and booted but recovery was gone (also using adb reboot recovery) made my phone go into bootloop
N8010 device with N8000 BL just to mention,
---------- Post added at 10:24 PM ---------- Previous post was at 10:22 PM ----------
lirokoa said:
Yes maybe the one for heap screenshot is not needed.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
@llirokoa do u know what lib is patched to fix the graphic issue? is it the surfaceflinger?
LastStandingDroid said:
it did remove my recovery after flashing this rom not sure why i was just unable to reboot to recovery (regular key combination)
used philz recovery rom worked and booted but recovery was gone (also using adb reboot recovery) made my phone go into bootloop
N8010 device with N8000 BL just to mention,
---------- Post added at 10:24 PM ---------- Previous post was at 10:22 PM ----------
@llirokoa do u know what lib is patched to fix the graphic issue? is it the surfaceflinger?
Click to expand...
Click to collapse
I've written quite big in the third post that you need to flash supersu beta just after the rom or you won't be able to boot into recovery: you've been warned. I'm working on merging the fixes for graphics issues.
By the way I've fixed the stylus input which is working ok now. New version soon....
New version 20141125 out
I've just uploaded a new build. See OP for download links and second post for changelog. Before signaling a bug or something that isn't working, please read the third post, too.
Another bug I've found is in charging off script, please recharge your tablet while on until next release
On my n8013, every time I flash the ROM, then gapps, then superSU, I get a boot loop, never makes it to Omni logo. I tried to redownload all files from the OP, and still no luck. Tried 4 times now
Rom updated on May 19. This is LP 5.1 release 2. Latest Google/CM/Resurrection sources + all hardened features. Plus cleaned IP addresses (got rid of Google, Level 3 communication, AT&T, Orange, Department of Defense and other shady ips). Also enabled is Volte (enhanced LTE), which is Voice over LTE. This depends on the service provided by your carrier. In the States, for example, T-Mobile provides such services, which include high definition voice. Usually, you need special update done by the manufacturer in conjunction with your carrier. This rom does not need that. Your Z1 is already provisioned for Volte. You will see in Mobile Settings another entry: Enhanced 4g LTE Mode. ALso, in test menu/phone (*#*#4636#*#*), you will see a Volte Provisioned Flag. So, as soon as your carrier starts Volte, you are all set.
Sources are the same...
Download Link: http://forum.xda-developers.com/devdb/project/dl/?id=12531
_____________________________________________________________________________________
Rom updated to latest sources on May 4. In addition to regular hardened features, more than 40 instances of Google IP, Level 3 Communication and Department of Defense IPs removed from sources both for IPV4 and IPV6. The same is replaced with Opendns IP. Keep in mind that those ips go not only in configuration files, but libs also and the latter cannot be decompiled and fixed...
Download link: http://forum.xda-developers.com/devdb/project/dl/?id=12289
______________________________________________________________________________________
Rom Updated to LP 5.1.1. All hardened/security features implemented. Kernel used from Slimroms 5.1.
TWRP 2.8.6 is integrated in kernel.
Obviously, this is an alpha version...
Download Link: http://forum.xda-developers.com/devdb/project/dl/?id=12110
Kernel Source: https://github.com/AOSP-Argon/kernel_sony_msm8974/tree/lp5.1
___________________________________________________________________________________________________
Rom updated to 5.1: all hardened features enabled.
Download link: http://forum.xda-developers.com/devdb/project/dl/?id=11901
___________________________________________________________________________________________________
March 31: kernel updated to include screen color calibration:
See Download link: http://forum.xda-developers.com/showpost.php?p=59801528&postcount=94
_________________________________________________________________________________________________
March 27: New build is up, latest CM and Resurect changes; kernel includes voltage table, syncookie and TWRP.
Download Link: http://d-h.st/lw2s
Mirror Link: http://forum.xda-developers.com/devdb/project/dl/?id=11744
_________________________________________________________________________________
March 15: New build is up including latest sources, TWRP integrated in kernel, led lights fixed
DOWNLOAD LINK: http://d-h.st/UO7W
_______________________________________________________________________________________________
Marchh 7: Rom Updated to the latest version + plus all security enhancements. Sources for security changes are the same as posted
See Download section for update
Here is Resurection Remixed Lollipop hardened and secure. Built from sources on February 24.
Changes:
First of all, as many know, encryption on lollipop slows down the device to almost unusable. I was able to resolve that. The culprit was Qualcom crypto module and drivers that collide with graphics. In this rom, when you encrypt your device, there is no noticeable slow down at all. Your master encryption key is no longer stored in crypto module (which rumor has it is backdoored anyway), but rather hashed and salted on the drive itself.
1. Modified kernel to disable creepy SElinux and enable Tomoyo security. Now you can safely use Xposed framework and some modules such as Xprivacy, Appsettings and ShowDialpad, as well as many others
2. Modified kernel to disable qualcom module and drivers
3. Disabled creepy qualcom random number generation and enabled all other methods
4. Enabled 256 bit AES drive encryption as opposed to Google's default 128 bit
5. Enabled all ciphers and hashes available in kernel and disabled by default (thanks Sony and Google)
6. Latest CM changes
7. Omniswitch (to be flashed separately after flashing the rom)
Maybe more
INSTALL:
1. Be on Kitkat, rooted with CWM or TWRP
2. Enter Recovery, wipe System, Data, Cache
3. Flash the rom
4. Flash Omniswitch
5. Reboot and enjoy
If you want to encrypt your device, you need to do 2 additional steps before or after encryption. Go to Developer Options and enable "Force GPU rendering" and "Disable HW overlays. Yes, you have to enable (not disable) "Disable HW overlays" option. The latter won't stick after reboot. So, manually transfer the attached init.d script to /system/etc/init.d and set permissions to at least 744. This way the option will be set at boot and you won't have any noticeable slowdown. In fact, I don't see any difference in speed between encrypted and non encrypted device.
CREDIT: Resurection-Remix Team, Cyanogenmod, AOSP and Omniroms
WARNING:
I am not responsible if your device explodes and kills everyone around. You are doing it on your own. Russians, who are definitely coming, won't help you either :laugh:
Download links
Rom: http://d-h.st/l1rB For Update see Download Section
Omniswitch: http://d-h.st/AbGH
Init.d script (in case you want to encrypt your data): http://d-h.st/QIiE
Sources: https://github.com/ResurrectionRemix
https://github.com/HonamiZ1/android_system_vold
https://github.com/HonamiZ1/kernel_sony_msm8974
XDA:DevDB Information
Resurection-Remixed Lollipop 5.1.1 Hardened, ROM for the Sony Xperia Z1
Contributors
optimumpro
ROM OS Version: Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: AOSP, Cyanogenmod
Version Information
Status: Testing
Created 2015-02-25
Last Updated 2015-05-19
screenshots
Screenshots added
Kernel updated with CPU voltage table
Kernel updated to allow under/over volting. See attachment.
Instructions:
1. Unzip the file
2. Flash in fastboot: fastboot flash boot boot.img and fastboot reboot
Enjoy
Thanks for this ROM, are there any known bugs?
wis3m0nkey said:
Thanks for this ROM, are there any known bugs?
Click to expand...
Click to collapse
All CM bugs as of February 24. You can go on their site and see the list of changes...
optimumpro said:
All CM bugs as of February 24. You can go on their site and see the list of changes...
Click to expand...
Click to collapse
So just need to look at http://forum.xda-developers.com/xperia-z1/general/rom-official-cyanogenmod-12-nightlies-t3007118 is that right?
Sorry I have to confirm, there are multiple threads (Official/Development) for CM12.
This ROM will maintain root and recovery, right?
I'll flash and let you know if I find any other issues.
Tried it. Works great. Some strange problem with mms though. Could not load them even though data works perfectly. Battery life looks great. Didn't try calling so i can't say anything about the mic.
Kyrius said:
Tried it. Works great. Some strange problem with mms though. Could not load them even though data works perfectly. Battery life looks great. Didn't try calling so i can't say anything about the mic.
Click to expand...
Click to collapse
I use Textsecure as sms replacement. Microphone works great...
Very buggy
you should definately fix this rom as i cannot start camera it fc. it restart itseft
NOT STABLE
darkdevu said:
you should definately fix this rom as i cannot start camera it fc. it restart itseft
NOT STABLE
Click to expand...
Click to collapse
1. Learn the rule about not posting bug reports without logcat
2. Camera works fine: verified
3. Always wipe System/Data/Cache before flashing
4. Are you sure you have Xperia Z1?
Cheers
his profile says Z3. lol
Any further reports on this ROM? Interesting to know how it performs and about stability
Deleted
wis3m0nkey said:
Thanks for this ROM, are there any known bugs?
Click to expand...
Click to collapse
Rom Updated to the latest version. See Download section in the OP.
and where is the link to the update?
shikimafia said:
and where is the link to the update?
Click to expand...
Click to collapse
It is in Download section:
http://forum.xda-developers.com/devdb/project/?id=8412#downloads
Screenshots added in post #2. Note that only this rom and SlimLP work with the latest Xpivacy module. Tried on Crdroid and others and there is bootloop as soon as you enable Xprivacy.
Has no one tried this rom as not reports or posts
tried flashing update from scratch and get play services fc on every gapps i used............i am guessing i may have to flash initial release and dirty flash this over it? excuse me if i may have got it wrong
shingers5 said:
Has no one tried this rom as not reports or posts
Click to expand...
Click to collapse
Well. The first version had 69 downloads. The latest one had 20. Other than the bogus claim about camera foreclosing (by someone who has Xperia Z3) there were no reports of problems. I have been using this rom for about 10 days without any problems...
optimumpro said:
Well. The first version had 69 downloads. The latest one had 20. Other than the bogus claim about camera foreclosing (by someone who has Xperia Z3) there were no reports of problems. I have been using this rom for about 10 days without any problems...
Click to expand...
Click to collapse
I'm having issues flashing the new version as getting play services errors.... Was gonna try dirty flash over previous versions
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.x (Nougat),
which is designed to increase performance and reliability over stock Android for your device.
All the source code for LineageOS is available in the LineageOS GitHub repo.
And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Official LineageOS website : http://lineageos.org
Downloads Links
LineageOS 14.x (Unlocked Bootloader) :
Nightlies : https://download.lineageos.org/odin
Google Applications (optional) :
OpenGapps : http://opengapps.org/ (Use packages for ARM, Android 7.x, Micro or Pico)
Information : Flash the GApps before the first boot. If not, a clean flash is recommended.
Informations and references :
About LineageOS updates : ChangeLog available on http://www.cmxlog.com/14.1/odin/
About LineageOS device side : See my GitHub trees linked below
Flashing and updating
LineageOS clean install :
- (Optional) Flash the boot.img kernel from the ROM zip with Fastboot or Flashtool
- (Optional) Wipe the data & cache (Backup to make sure not to loose data)
- Flash the LineageOS ROM zip from the Recovery
- (Optional) Flash the GApps to have the Google Applications
- (Optional) Every additional zip you want to flash
- Reboot
LineageOS update / upgrade :
- (Information) Don't wipe anything unless you want to
- (CM / UNOFFICIAL) Nothing to wipe when switching
- (FUTURE RELEASES) Might need clean, informations will be updated
- Flash the latest LineageOS ROM zip from the Recovery
- (Optional) Flash the GApps on first install / upgrade. Not required later, but do update sometimes
- (Optional) Every additional zip you want to flash
- Reboot
LineageOS addonsu for root access :
- (Information) Read the Root section of the Q&A thread
- (Download) Download the addonsu for arm : LineageOS Downloads / Extras
- (Optional) Flash the zip on a working Lineage installation (once)
- (Information) Upon ROM updates, the addonsu is preserved
- Reboot
About the builds
Device tree : https://github.com/fusion3-common/android_device_sony_Odin/commits/cm-14.1
Kernel sources : https://github.com/fusion3-common/android_kernel_sony_apq8064/commits/cm-14.1
Vendor blobs : https://github.com/fusion3-common/proprietary_vendor_sony/commits/cm-14.1
Issues and reports
- Report issues only if you are using the ROM kernel
- If an additional mod is installed, make sure it's unrelated, and mention it
- Make sure the issue wasn't discussed earlier in the threads
- Share a log of the error with CatLog for example
About LineageOS Legal : http://lineageos.org/legal/
The LineageOS team would like to thank everyone involved
in helping with testing, coding, debugging & documenting! Enjoy!
[/INDENT]
LineageOS available for Odin also thanks to :
- The LineageOS Team
- The CyanogenMod Team
- Everyone involved in working and testing
XDA:DevDB Information
[ROM][NIGHTLIES][7.1] LineageOS 14.1 for Xperia ZL, ROM for the Sony Xperia ZL
Contributors
Daedroza, AdrianDC, Chippa_a, Olivier, Namelos, CyberwalkmaN, sigprof
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Version Information
Status: Testing
Created 2017-07-17
Last Updated 2017-11-10
Reserved
FEATURES AND ISSUES
Code:
- Boot : Ok
- GApps : OpenGApps Micro Ok
- FOTA Recovery : Ok (see below)
- WiFi : Ok (real SONY MAC address)
- Bluetooth : Ok (real SONY MAC address)
- WiFi Hotspot : Ok (2.4GHz and 5GHz)
- RIL - Phone - Data : Ok
- GPS : Ok
- Camera : Ok
- Camcorder : Ok
- Lights : Ok
- MicroSD : Ok
- Accelerometer : Ok
- Compass : Ok
- Gyroscope : Ok
- AOSP sensors : Ok
- FM Radio : Ok
- Vibrator : Ok
- Microphone : Ok
- Audio & external audio : Ok
- Bluetooth audio : Ok
- NFC : Ok
- Kernel : Ok, Updating frequently
- Graphics : Ok
- 3D Rendering : Ok
- Clock : Ok
- Offline Charging : Ok
- SEPolicies : Fully enforced
Thanks and good luck on getting this official.
Thanks for your hard work,it works fine
Successfully upgraded from Chippa_a's unofficial Lineage 170413 build without wipe. Thanks.
after bootind in recovery (twrp), wiped cache and data, flashed the zip lineage-14.1-20170716-UNOFFICIAL-odin.zip and open_gapps-arm-7.1-mini-20170722.zip and rebooted. After that, only black screen and no boot into system, only fastboot or flash mode...
previously using a stock rom in 5.1.1 with root and recovery.
any help?
ps: after that, tried to flash the boot.img in fast boot mode, get this error:
>fastboot flash boot c:\boot.img
sending 'boot' (14972 KB)...
OKAY [ 0.293s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.297s
PS 2: tried flashing a ftf via flashtool, but get some errors too...
23/036/2017 18:36:01 - INFO - Opening device for R/W
23/036/2017 18:36:03 - INFO - Reading device information
23/036/2017 18:36:12 - INFO - Unable to read from phone after having opened it.
23/036/2017 18:36:12 - INFO - trying to continue anyway
23/036/2017 18:36:12 - INFO - Phone ready for flashmode operations.
23/036/2017 18:36:12 - INFO - Opening TA partition 2
23/036/2017 18:36:12 - INFO - Start Flashing
23/036/2017 18:36:12 - INFO - No loader in the bundle. Searching for one
23/036/2017 18:36:16 - INFO - Processing loader.sin
23/036/2017 18:36:16 - INFO - Checking header
23/036/2017 18:36:16 - ERROR - Processing of loader.sin finished with errors.
23/036/2017 18:36:16 - INFO - Ending flash session
23/036/2017 18:36:16 - ERROR - Error in processHeader : 22 : O dispositivo não reconhece o comando.
23/036/2017 18:36:16 - ERROR - Error flashing. Aborted
23/036/2017 18:36:16 - INFO - Device disconnected
@saddambea looks like you bootloader is not unlocked. Is that possible? If you back up you TA partition with twrp and recover from those backups you will relock your bootloader.
NamenIos said:
@saddambea looks like you bootloader is not unlocked. Is that possible? If you back up you TA partition with twrp and recover from those backups you will relock your bootloader.
Click to expand...
Click to collapse
yes, i think it´s possible, my bl may be locked. couldn´t unlock via fastboot after that
and now, i can´t even boot to recovery. tried to flash recovery.img through fastboot with no success...
saddambea said:
yes, i think it´s possible, my bl may be locked. couldn´t unlock via fastboot after that...
Click to expand...
Click to collapse
What error did you get? Maybe you have to go back to stock via flashtool for this.
saddambea said:
... and now, i can´t even boot to recovery.
Click to expand...
Click to collapse
This should be normal if you used Dual Recovery on the stock rom before. Dualrecovery is on the /system partition, that you wiped while flashing.
saddambea said:
... tried to flash recovery.img through fastboot with no success...
Click to expand...
Click to collapse
This can't work as we don't have have a recovery partition. Our recovery is either in the boot.img or the system partition. LineageOS uses the boot.img and optionally then boots the recovery in the FOTA Kernel partition if you press vol up.
Uploading a new build as we speak. The changelog since 2016 is (I'm just being vague here, I don't remember all the issues, but I do have all the logs with me, if someone is interested):
1. Fix ancient F2FS bug (Specific to Fusion3)
2. Fix https://forum.xda-developers.com/showpost.php?p=69849473&postcount=1243
3. Fix https://forum.xda-developers.com/showpost.php?p=68245138&postcount=1130
4. Fix for input_evdev specific to us
5. Fix for SWAP
6. Fix for C5502 Double Tap to Wake Screen Freeze.
7. Many other improvements like ZRAM / Process Reclaim / Perf / mmc / Anon Reclaim etc
8. Changes from Chippa_a for XML audio configuration is also picked, I don't know maybe you will see a improvement @gorillanobka?
I haven't gone much into detail, but please send logs (dmesg / last_kmsg / logcat) wherever possible if you face something. At the moment, I only have C5502 (Fusion3 Dogo) with me. Yuga / Odin has hardware specific to them (other than chipset), so I won't be able to reproduce them on my device if you get some event changes / sensors changes.
I've also included a minor hack for auto-brightness. Let me know how you feel about it.
Please give it a go? Thanks
Thank you Daedroza!
You're a scholar and a gentleman. Gimme a week or so ( I am caught up with assignments and exams ) and i will have a look at it...
I'm pretty sure it will be a super stable build as always...
I am already running a Chippa's build with some changes to the XML audio if i am not wrong, and i could already hear some improvements.
The notifications remained very low though... I think the EU specific limitation for the audio needs to be commented / removed in order to see serious improvements .
Kind regards
Gorilla no Baka
Daedroza said:
Uploading a new build as we speak. The changelog since 2016 is (I'm just being vague here, I don't remember all the issues, but I do have all the logs with me, if someone is interested):
1. Fix ancient F2FS bug (Specific to Fusion3)
2. Fix https://forum.xda-developers.com/showpost.php?p=69849473&postcount=1243
3. Fix https://forum.xda-developers.com/showpost.php?p=68245138&postcount=1130
4. Fix for input_evdev specific to us
5. Fix for SWAP
6. Fix for C5502 Double Tap to Wake Screen Freeze.
7. Many other improvements like ZRAM / Process Reclaim / Perf / mmc / Anon Reclaim etc
8. Changes from Chippa_a for XML audio configuration is also picked, I don't know maybe you will see a improvement @gorillanobka?
I haven't gone much into detail, but please send logs (dmesg / last_kmsg / logcat) wherever possible if you face something. At the moment, I only have C5502 (Fusion3 Dogo) with me. Yuga / Odin has hardware specific to them (other than chipset), so I won't be able to reproduce them on my device if you get some event changes / sensors changes.
I've also included a minor hack for auto-brightness. Let me know how you feel about it.
Please give it a go? Thanks
Click to expand...
Click to collapse
Thank you for continuing with this phone. I plan to download this new build momentarily and try, but I have two long running issues and wonder if you might comment.
One is that this seems to come from the C6503 which has a different set of cellular bands, and I think that means my C6506 cannot access them. Is that correct? I seem to have poorer coverage in some areas than with the stock Sony software (which is now ancient of course). I have no done a deep dive to see, other than to see cynogenmod now lineage seems to be specific to the less-bands phone modem?
The more specific question is this: after some days or weeks, the phone's display gets laggy on scrolls; two specific places I use a lot are the CNN app and the News360 app. I found a fresh install cleared it up nicely, then over time it gets worse. I experimented (takes a long time as it is reproducible only over a long time) and found it is the Dalvik cache. If I clear that and reboot -- smooth as silk. A couple weeks later, have to do it again. Any thoughts as to what is happening? It's easily fixable now that I know a full install is not needed, but it just seems strange. Anyone else seeing it? Try wiping just Dalvik, see if it helps.
Linwood.Ferguson said:
Thank you for continuing with this phone. I plan to download this new build momentarily and try, but I have two long running issues and wonder if you might comment.
One is that this seems to come from the C6503 which has a different set of cellular bands, and I think that means my C6506 cannot access them. Is that correct? I seem to have poorer coverage in some areas than with the stock Sony software (which is now ancient of course). I have no done a deep dive to see, other than to see cynogenmod now lineage seems to be specific to the less-bands phone modem?
The more specific question is this: after some days or weeks, the phone's display gets laggy on scrolls; two specific places I use a lot are the CNN app and the News360 app. I found a fresh install cleared it up nicely, then over time it gets worse. I experimented (takes a long time as it is reproducible only over a long time) and found it is the Dalvik cache. If I clear that and reboot -- smooth as silk. A couple weeks later, have to do it again. Any thoughts as to what is happening? It's easily fixable now that I know a full install is not needed, but it just seems strange. Anyone else seeing it? Try wiping just Dalvik, see if it helps.
Click to expand...
Click to collapse
- No idea about phone coverage. I had preferred if you could do a diff with signal measuring app or something of sort? That would give you a base stock result and one from Lineage.
- The phone's display gets slow / laggy / unresponsive systemwide or it just the apps? Maybe both the apps consume a lot of space on internal and cache. Hence you need to clear them.
On the original firmware there was a dialer code to show usable bands; it does not work on LineageOS. I have tried without success to find a way to tell which bands are supported in the current OS. With some playstore apps I can see the current band but not all usable bands.
The original C6506 (odin rimy) documentation listed the bands available, and compared to the C6503 (odin gina). There are a number of differences. The C6506 supports LTE I, IV and XVII that the C6503 does not; the C6503 supports LTE III, VII, VIII and XX that the C6506 does not. My understanding (but I am not certain) is that this is a hardware limitation of the device, which of course corresponds to the stock firmware. It could also be that the radios are the same, but the restriction on bands was purely in software tied to the model.
My reading of old postings on the cynogenmod software was it was based on the C6503, and so my question is what is the result. It seems POSSIBLE that it only then supports the bands they had in common: LTE I and V, which leaves a lot missing. Or it is also POSSIBLE that it supports all the C6503 bands which (again, my loose understanding) were not ideal for US/AT&T use, which is what the C6506 was fo.
Basically I know only enough to wonder if the LineageOS is limiting the bands the phone can use? And how I might tell for sure? And/or if you have all the source, can you tell, or is this buried in the blobs that are opaque?
As to the laggy: I think it is the whole system, but it is hard to say as I'm generally using some app. They do begin to start up slower as well as operate slower, but it is most noticeable on things that scroll. Frankly I would likely not notice other slowness if the scrolling did not hesitate. A list of stories in the CNN app, for example, if you touch and start scrolling hesitates nearly a second before it moves. Clear dalvik and there's no hesitation. It is also worth noting I use very little on the phone - mail, CNN, News360, weatherbug, calendar, and the phone are just about it. All visible resources (that I know how to look at) show lots of free space. Now that I know how to quickly fix it not a big deal.
Does the IR blaster work with this build? Does it work with other apps like Anymote?
According to Sonys whitepaper the C6506 should support LTE Band I, Band II, Band IV, Band V and Band XVII (1, 2, 4, 5 and 17). The supported bands are stored in partitions not touched by LineageOS (see here). You have to check which bands your provider uses in your region and then use an app to check if you get connected to which band, I don't think there is an alternative. The old dialer code won't work, as it is sony specific. I too haven't found an app that shows available LTE networks regardless of your contract and possibly this is not even possible on standard Android APIs.
Performance (in scrolling and in general) doesn't seem worse than on stock for me (in fact it feels better). I use F2FS, but I doubt it changes anything on your performance problems. Once we get all this in the official repos and get a weekly build status, there will probably be some experimental stuff that will be tried out and surfaces here. For now the focus is more on getting the officially supported status.
edit:
JLBouras said:
Does the IR blaster work with this build? Does it work with other apps like Anymote?
Click to expand...
Click to collapse
Only with one app (the one that worked on CM13), root access and selinux disabled, we have to add file permissions, ownership and selinux rules. This is not yet tested enough though. edit: Just tested with selinux disabled, works well with preconfigured remotes, slightly flaky when learning imo.
NamenIos said:
According to Sonys whitepaper the C6506 should support LTE Band I, Band II, Band IV, Band V and Band XVII (1, 2, 4, 5 and 17). The supported bands are stored in partitions not touched by LineageOS ....
The old dialer code won't work, as it is sony specific. I too haven't found an app that shows available LTE networks regardless of your contract and possibly this is not even possible on standard Android APIs.
Click to expand...
Click to collapse
That's the list of the supported bands, but I know I read years ago that the (not sure if this is the right word?) modem used by Cynogenmod for this phone started as the 6503. Does the software incorporated within LineageOS support all bands listed in the partition mentioned?
I tried to find the old discussion I remember without success. Closest I got was this which brings it up (look for "bands"), but people are saying "mine works". The issue of course is if some bands work but not others the phone may "work" but not have the same coverage where you have less bands or more congestion.
I was hoping there was a way to actually query the phone for which have actual hardware+software support, but it sounds like there no longer exists that ability with the loss of that service menu.
NamenIos said:
Performance (in scrolling and in general) doesn't seem worse than on stock for me (in fact it feels better). I use F2FS, but I doubt it changes anything on your performance problems. Once we get all this in the official repos and get a weekly build status, there will probably be some experimental stuff that will be tried out and surfaces here. For now the focus is more on getting the officially supported status.
Click to expand...
Click to collapse
Frankly it may have been the same there. I'm wondering if, being news related apps I use most, if they are leaking/cluttering up the cache in some way more than normal use (Dalvik is for the VM, right? Do apps cache data there or just the VM cache app code there?). Regardless, I have an easy workaround, it takes just a few minutes to clear and get back fully up.
I absolutely agree getting fully supported is great. I hope to get a Pixel2 when they come out, and leave this as a backup phone, so would love to get a few more years utility out of it. It's been a really great phone, I still rarely see any with the low percentage of wasted space on the front as this.
Linwood.Ferguson said:
That's the list of the supported bands, but I know I read years ago that the (not sure if this is the right word?) modem used by Cynogenmod for this phone started as the 6503.
Click to expand...
Click to collapse
Modem partitions are not affected in case of installation of LineageOS/CyanogenMod. This ROM is universal for all models (C6502/6503/6506).
NamenIos said:
The supported bands are stored in partitions not touched by LineageOS
Click to expand...
Click to collapse
New build is up folks.
- Security patches till July 2017.
- Clean build, inclusive of all changes by LineageOS till yesterday.
- Includes DRM libraries.
- All other standard bugfixes from cm-13.0 thread, all of them. YES, all of them.
- Attempt to fix a problem as told here (https://forum.xda-developers.com/showpost.php?p=73250499&postcount=16)
Folks, this has been a year long journey for me, let's face it, I am learner, so I need your feedback here. Even a smallest problem (like force closes) will seen as long as you provide logs. Regarding stability, we're not pushing devices that reboot or mess up after some time. A lot of people are involved in completing this and I would like to thank all of them. And good feedbacks are welcome too, if it works for you
Daedroza said:
New build is up folks.
- Security patches till July 2017.
- Clean build, inclusive of all changes by LineageOS till yesterday.
- Includes DRM libraries.
- All other standard bugfixes from cm-13.0 thread, all of them. YES, all of them.
- Attempt to fix a problem as told here (https://forum.xda-developers.com/showpost.php?p=73250499&postcount=16)
Folks, this has been a year long journey for me, let's face it, I am learner, so I need your feedback here. Even a smallest problem (like force closes) will seen as long as you provide logs. Regarding stability, we're not pushing devices that reboot or mess up after some time. A lot of people are involved in completing this and I would like to thank all of them. And good feedbacks are welcome too, if it works for you
Click to expand...
Click to collapse
And just a day later, August Security Patches was released...
Based on Demetris' LOS 14.1, with :
Android security patch level updates, currently 2020-02-05
tracking LA.BR.1.2.9 from CAF, currently 1.2.9_rb1.44
WIP upstream with linux-stable, currently upgraded from 3.10.49 to 3.10.68 3.10.75
SELinux enabled (better security, SafetyNet & PlayStore should be ok, if not check @tess1 clear caches post )
2018 fixes : MTP, battery consumption, camrecorder crash, wifi, OpenGL ES version, dualsim 6045K (update to MM first), lid & proximity sensor
known problems :
camrecording low brightness
mobile internet connectivity loss and battery drain after a while (days) : toggle airplane mode and back, or reboot
new problems : none known at the moment, but the ROM is not so thoroughly tested before publication
How to investigate and report problems :
sudo adb shell dmesg > dmesg.txt
sudo adb logcat > logcat.txt
sudo adb logcat -b radio > radio.txt
Credits : @FireLord, @Demetris, @Unjustified Dev and all the giants whose shoulders we stand upon !
Source code : Kernel | Device | Vendor trees | Local manifest : View attachment idol3.xml
Changes since previous build : see the build release post
Downloads : lineage-14.1-20200226-UNOFFICIAL-idol3.zip | other releases
Kernel alternative (cam might not work since 20190619 build) : overclocked kernel by @DepressedHedgehog
Reserved
Thanks a lot for sharing this build. Now that the method for restoring our phones to stock has been taken away from us, I'm hoping that more people will jump in and try to solve some of the few remaining issues with this ROM.
Personally I'd like to figure out why the Play Store is installing old versions of certain apps and listing other apps as being incompatible while they can be still sideloaded without any problem. I've found many threads on XDA with people complaining about the same issue but no solution that worked so far. Is this an issue with opengapps, or bad entries in the build.prop? I've compared with the original build.prop from stock 6.0.1 and tried changing values around but no success.
Also battery life seems a lot shorter with Nougat, and there is no way to find out which apps/processes are being power hungry as you have already pointed out.
Issues aside this ROM still makes this phone quite usable and stable compared with other ROM's I have tried so good job and I'm looking forward to testing out new builds.
new thread - we're open for business!
@vknecht once again, thanks for your continued efforts... I tried your Sept 12 release with opengapps Sept. 12 as well - the Play store continues to thwart our efforts in the same manner.
@upyisfar I found that the battery drain during sleep could be reduced to almost nil with the following settings:
- turn off WIFI during sleep - Settings-> WIFI -> Gear Icon -> Keep WIFI on during sleep -> change to....
- turn off Emergency Broadcasts - Settings -> ...More ->Emergency Broadcasts -> Uncheck all
20180918 build : add ptt_socket_app for better wifi and battery
This was a complain in the logs, so added it from MM.
There are still batterystats related problems but there's a lead...:
Code:
09-19 15:14:35.466 1192 1344 E BatteryStatsService: no controller energy info supplied
09-19 15:14:35.748 1192 1212 E BatteryStatsService: power: Missing API
09-19 15:14:35.762 1192 1344 E BatteryStatsService: modem info is invalid: ModemActivityInfo{ mTimestamp=0 mSleepTimeMs=0 mIdleTimeMs=0 mTxTimeMs[]=[0, 0, 0, 0, 0] mRxTimeMs=0 mEnergyUsed=0}
Thanks @upyisfar @tess1 for the feedback, keep us posted with your findings...
@vknecht
1. Just tried something... reinstalled 7/18 build where all of the play store program installations were working and then overlayed it with OTA 9/18 which then led to PLay Store blocking installation of many apps ("device isn't compatable" error) - I recall that the build after 7/18 included 25 fixes/commits. Not easy to track it down but could the problem be from one of those fixes/commits?
2. The proximity sensor (tsl2772-ps) error was earlier reported as either missing a driver or needing a shim. Is this a file that can be pulled from Marshmallow and put into this ROM?
Battery updates to follow
vknecht said:
This was a complain in the logs, so added it from MM.
There are still batterystats related problems but there's a lead...:
Click to expand...
Click to collapse
Interesting. How do we know if those changes were merged into the LineageOS's code repo?
vknecht said:
[*]SELinux enabled (helps with safetynet basicIntegrity test ; also better security, but some glitches here and there)
[*]new problems : probably due to SELinux now in "enforce" mode, like battery stats
Click to expand...
Click to collapse
I've installed your new build last night and I've set my kernel to run in permissive mode (Magisk SELinux Manager module) and safetynet basicIntegrity test still passes just so you know. Battery life now feels more comparable to what I get in stock MM. Not sure if this due to SELinux being switched to permissive or the the changes that you have made.
What build environment are you using to build your ROM's, I'm trying to build on Debian stable following your instructions here and keep getting compilation errors.
tess1 said:
@vknecht
1. Just tried something... reinstalled 7/18 build where all of the play store program installations were working and then overlayed it with OTA 9/18 which then led to PLay Store blocking installation of many apps ("device isn't compatable" error) - I recall that the build after 7/18 included 25 fixes/commits. Not easy to track it down but could the problem be from one of those fixes/commits?
Click to expand...
Click to collapse
I thought the 20180905 build ruled out the august kernel updates as the breaker but in fact I should and will retry kernel from july with SELinux enabled ; if it's still not OK then I guess the cause is LOS august update...
tess1 said:
2. The proximity sensor (tsl2772-ps) error was earlier reported as either missing a driver or needing a shim. Is this a file that can be pulled from Marshmallow and put into this ROM?
Click to expand...
Click to collapse
iiuc the hint is that we need either a HAL/framework wrapper OR reuse stock Lollipop driver+shim.
I'm sorry I don't know much about this low-level androidy stuff yet and don't have much time atm to focus on it.
upyisfar said:
Interesting. How do we know if those changes were merged into the LineageOS's code repo?
Click to expand...
Click to collapse
I think if it was in LOS it should appear here : https://github.com/LineageOS/android_system_extras/commits/cm-14.1/ext4_utils
upyisfar said:
I've installed your new build last night and I've set my kernel to run in permissive mode (Magisk SELinux Manager module) and safetynet basicIntegrity test still passes just so you know. Battery life now feels more comparable to what I get in stock MM. Not sure if this due to SELinux being switched to permissive or the the changes that you have made.
What build environment are you using to build your ROM's, I'm trying to build on Debian stable following your instructions here and keep getting compilation errors.
Click to expand...
Click to collapse
I'm using Fedora 28 ; note that you'd have to update the local manifest ($ANDROID_ROOT/.repo/local_manifests/idol3.xml) using given kernel/device/vendor trees as linked in OP, so at the moment it should look like :
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="vknecht/android_device_alcatel_idol3" path="device/alcatel/idol3" remote="github" revision="fix-ptt_socket_app" />
<project name="vknecht/android_kernel_alcatel_msm8916" path="kernel/alcatel/msm8916" remote="github" revision="upstream-lxstable-cafrb144" />
<project name="vknecht/proprietary_vendor_alcatel" path="vendor/alcatel" remote="github" revision="fix-ptt_socket_app" />
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-14.1" />
</manifest>
(to use july kernel change revision to "upstream-lxstable").
For idol3 build environment setup help, feel free to send me private messages or join #idol3 on Freenode, or maybe even create a thread, for the more we are able to build, the better...
vknecht said:
I thought the 20180905 build ruled out the august kernel updates as the breaker but in fact I should and will retry kernel from july with SELinux enabled ; if it's still not OK then I guess the cause is LOS august update...
iiuc the hint is that we need either a HAL/framework wrapper OR reuse stock Lollipop driver+shim.
I'm sorry I don't know much about this low-level androidy stuff yet and don't have much time atm to focus on it.
Click to expand...
Click to collapse
1 Just tried the 9/05 build --> same play store issue --> August updates maybe problematic
2 Fair enough... I don't know enough but am willing to beta test along the way
It is all in progress...
tess1 said:
1 Just tried the 9/05 build --> same play store issue --> August updates maybe problematic
2 Fair enough... I don't know enough but am willing to beta test along the way
It is all in progress...
Click to expand...
Click to collapse
I've tried the july 3.10.68 kernel (used in 20180718 and 20180905 builds) with current device/vendor trees, and still G compat problems, so it leaves the Android/LineageOS diffs from 2018-06-05 to 2018-08-05 patch levels (afaik there was no 2018-07-05 for LOS 14.1 and there's no 2018-09-05 yet).
20180924 build : 2018-09-05 android security patch level
Only change is Android/LineageOS framework (repo sync) for 2018-09-05 update
Too sad, it doesn't seem to solve the some-apps-in-proeminent-vendor-store incompatibility problem...
@upyisfar : I've wondered about "the method for restoring our phones to stock has been taken away from us", what did you mean ?
While, too bad, the Sugar utility (which had my preference) now fails on a "site not found" error (maybe should try a fresh install, why not in Wine), I still could reset by using the "Panasonic Eluga Switch" utility then the "Mobile Q upgrade" (~1 hour total, with 100Mbs connection) to go back to stock.
lineage-14.1-20180924-UNOFFICIAL-idol3.zip | or OTA zip
Q
vknecht said:
I've wondered about "the method for restoring our phones to stock has been taken away from us", what did you mean ?
While, too bad, the Sugar utility (which had my preference) now fails on a "site not found" error (maybe should try a fresh install, why not in Wine), I still could reset by using the "Panasonic Eluga Switch" utility then the "Mobile Q upgrade" (~1 hour total, with 100Mbs connection) to go back to stock.
Click to expand...
Click to collapse
The Sugar utility was what I was referring to. Haven't had any success with the Mobile Q though, I always get a "check your internet connection" message or something like that. The MM 6.0.1 ROM posted by The Marionette is close enough though. I don't expect Alcatel to push more OTA updates for this device anyway.
I'm sticking with your build of Nougat now that the battery drain issue has gone away. I don't mind manually transfering the APK's from another device to my phone, for now at least. I have managed to set up my build environment (was missing a dependency) and will be producing a test build soon to see if I can fix a thing or two. In the mean time I will happily upgrade to the new build that you have just posted. Thanks!
upyisfar said:
The Sugar utility was what I was referring to. Haven't had any success with the Mobile Q though, I always get a "check your internet connection" message or something like that. The MM 6.0.1 ROM posted by The Marionette is close enough though. I don't expect Alcatel to push more OTA updates for this device anyway.
I'm sticking with your build of Nougat now that the battery drain issue has gone away. I don't mind manually transfering the APK's from another device to my phone, for now at least. I have managed to set up my build environment (was missing a dependency) and will be producing a test build soon to see if I can fix a thing or two. In the mean time I will happily upgrade to the new build that you have just posted. Thanks!
Click to expand...
Click to collapse
@upyisfar
Just 3 weeks ago, I was able to restore (in Canada) my Idol 3 to stock MM using Mobile Upgrade (I think it was version 5.1.7 as 5.1.8 would not do anything).
Here is an upload link:
5.1.7:
https://mega.nz/#!KmogkYAa!e5y6ZSM987quN6bTYRNWnZuNQSBnCjANMglrhB4rtHo
5.1.8:
https://mega.nz/#!OuhEGaaQ!g6mH6RE7v7MEGSI5-uWsr_t4MZCX3qh1fmCtHzhHptI
I put the phone into download mode and it took about 30 minutes.
---------- Post added at 10:45 PM ---------- Previous post was at 10:39 PM ----------
@vknecht
vknecht said:
This was a complain in the logs, so added it from MM.
There are still batterystats related problems but there's a lead...:
Code:
09-19 15:14:35.466 1192 1344 E BatteryStatsService: no controller energy info supplied
09-19 15:14:35.748 1192 1212 E BatteryStatsService: power: Missing API
09-19 15:14:35.762 1192 1344 E BatteryStatsService: modem info is invalid: ModemActivityInfo{ mTimestamp=0 mSleepTimeMs=0 mIdleTimeMs=0 mTxTimeMs[]=[0, 0, 0, 0, 0] mRxTimeMs=0 mEnergyUsed=0}
Thanks @upyisfar @tess1 for the feedback, keep us posted with your findings...
Click to expand...
Click to collapse
re: add ptt_socket_app for better wifi and battery
Would it be possible for you to list the (hopefully few) files and any edited files that you put into this build and the corresponding locations so that I can graft them onto my 7/18 build?
tess1 said:
Just 3 weeks ago, I was able to restore (in Canada) my Idol 3 to stock MM using Mobile Upgrade (I think it was version 5.1.7 as 5.1.8 would not do anything).
Here is an upload link:
5.1.7:
https://mega.nz/#!KmogkYAa!e5y6ZSM987quN6bTYRNWnZuNQSBnCjANMglrhB4rtHo
5.1.8:
https://mega.nz/#!OuhEGaaQ!g6mH6RE7v7MEGSI5-uWsr_t4MZCX3qh1fmCtHzhHptI
I put the phone into download mode and it took about 30 minutes.
Click to expand...
Click to collapse
OK. I was wondering if Alcatel was geo-blocking some countries seeing how some people have success and others don't. I'm in Canada too so I guess that isn't the issue. For now I'm more interested in trying to find a solution to the opengapps compatibility problem.
---------- Post added at 11:04 PM ---------- Previous post was at 10:51 PM ----------
tess1 said:
[MENTION=9435528]
re: add ptt_socket_app for better wifi and battery
Would it be possible for you to list the (hopefully few) files and any edited files that you put into this build and the corresponding locations so that I can graft them onto my 7/18 build?
Click to expand...
Click to collapse
See these commits https://github.com/vknecht/propriet...mmit/f84888778905c179e0d49d7587bc5467248e4b01 and https://github.com/vknecht/android_...mmit/dc64e2c79616e33640a2680451e2fe5ab0152d89
... and the workaround for disabling the bogus 3rd camera mode
https://github.com/vknecht/propriet...mmit/b57afd7960943e0dc8f0c593ae25cb74b5351a3f
6045K / dualsim / multisim
Code:
idol3:/ # setprop ctl.start ril-daemon1
Does it make it better for you too ? (dunno if there's a non-root or GUI equivalent...)
Good news!
I have found the fix for the opengapps store compatibility issue.
I noticed in CPU-z that the reported OpenGL ES version was 1.0 so I added a line to my build.prop:
Code:
ro.opengles.version=196609
And now CPU-z reports version OpenGL ES version 3.1 and all my apps are available for download in the G store.
the value "196609" is decimal for hexadecimal 30001 (OpenGL ES 3.1). Ive seen a commit on github that says support for 3.2 was added but when I change the value to "196610", CPU-z still reports 3.1 not sure why..
vknecht said:
new problems : probablymaybe due to SELinux now in "enforce" mode, like battery stats
Click to expand...
Click to collapse
Appears to be working since the 2 latest builds, with SELinux set to enforce:
[/COLOR]
upyisfar said:
Good news!
I have found the fix for the opengapps store compatibility issue.
I noticed in CPU-z that the reported OpenGL ES version was 1.0 so I added a line to my build.prop:
Code:
ro.opengles.version=196609
And now CPU-z reports version OpenGL ES version 3.1 and all my apps are available for download in the G store.
the value "196609" is decimal for hexadecimal 30001 (OpenGL ES 3.1). Ive seen a commit on github that says support for 3.2 was added but when I change the value to "196610", CPU-z still reports 3.1 not sure why..
Click to expand...
Click to collapse
SECONDED - Confirmed fixed! and the Play Store also reports that my Device is Certified under Play Protect Certification.
Thank you upyisfar
vknecht said:
Code:
idol3:/ # setprop ctl.start ril-daemon1
Does it make it better for you too ? (dunno if there's a non-root or GUI equivalent...)
Click to expand...
Click to collapse
6045I single-sim here, can't test this, sorry.
BTW can you add "low brightness in camera video capture mode" to list of known issues in the op? thx