Related
An official OTA for GSM Nexus S (GT-i9020T/i9023) is now available:
http://android.clients.google.com/packages/ota/google_crespo/9ZGgDXDi.zip (thanks bl1nkk)
Because an official release is now available, this ROM is now EOL and will receive no further support.
By popular demand, here's a new thread for my port of the Jelly Bean SDK. This is a continuation of DaxMax's thread, so if you want to see previous discussion, look there. (Thanks to DaxMax for putting up with discussion of what is essentially a distant cousin of his original ROM for so long on his thread.)
http://files.mrks.me/update-crespo-JRN83C-preview-2012063001.zip http://goo.gl/40Cxf (thanks to bl1nkk for the hosting)
Code:
MD5: 015e322b048b7e1464a90a87a5a6bcb1
SHA1: 3aca40900b40625505d4b6c0afce93c31e33770d
SHA256: 3b0b76444c307f4ffe685205cb92ad6060d957152dadef72444b3f2407510a34
Service Pack 4 for this ROM: https://docs.google.com/uc?export=download&id=0BwGWbMaI9twWRHFrRUROcDhIeVk http://goo.gl/ZVlQS (many thanks to bl1nkk for hosting) (alternately, check thread for mirrors) (see this post for changelog)
Code:
MD5: ac85b1e309ba3a3f438efe0954c11c32
SHA1: d147f777f8594c5d33dfd480143758107ff1baab
SHA256: 951d39e75e8d4891e18a1da3896567f293074262d8aef3cd0021d4239492cf00
Flash the main ROM zip (update-crespo-JRN83C-preview-2012063001.zip) first, then the service pack.
These are zips which should be flashable from ClockworkMod or other recovery. They contain /system and a boot.img and will not touch your recovery, data, or SD card. I believe you need to do a full wipe if you're flashing over ICS or below.
This ROM is quite stable and almost fully working at this point. Highlights:
Based on the Jelly Bean SDK release (JRN83C), with Google apps and other components from the Nexus 7 factory image (JRN84D). Hardware-related files and kernel from the ICS IMM76D release for Nexus S. (The source for the GPL components (mainly the kernel) is available from http://android.googlesource.com/.) The wifi hack (libhardware_legacy.wifi.so) is posted farther down this thread (including source).
Remarkably smooth. Project Butter really lives up to its name. (I've made one tweak in the init.herring.rc to make the default ICS cpufreq governor more aggressive in upping the clock frequency, in order to simulate the change in governor in the Jelly Bean kernel.)
Wifi, Bluetooth, GPS, GSM all work. NFC should work.
Sound and calls work as of July 9 (SP1).
Video recording works as of July 10 (SP2).
Tethering, including wifi tethering, works as of July 11 (SP3).
Calls via a Bluetooth headset work as of July 11 (SP3).
Google Now/voice search, offline voice text input, voice dialing, and text-to-speech all work as of July 11 (SP4).
Broken:
Voice/video chat in Google Talk Patch available to fix video/voice chat, see this post. (thanks selectormoldy for the crash log leading to fix)
Media scanning (used by Gallery and Music to find files on the SD card, among other things) is broken for some, but not for others. This appears to be triggered by something stored on the SD card/external storage. (thanks spupuz)
High-performance WifiLocks (the wifi driver drops into low-power mode when the screen turns off, even though it shouldn't when a high-perf WifiLock is held).
Sound. Note that means no phone calls of any kind, not even emergency calls, so this isn't ready for serious day-to-day use. This is likely unreasonably difficult to solve given that we have an official OTA coming in 2-3 weeks; look upthread for an account of what's been tried.
Ambient light sensor. It worked in the Galaxy Nexus-based ROM, and I'm not sure why it doesn't work in this one; in any event I'm not planning on putting more time into figuring out why. The light sensor works, but automatic brightness setting does not -- presumably something in the Android framework needs to be changed.
Video recording (as reported by users in this thread).
The Google Now/Google Search app may crash (reported by users in this thread). (This should be fixed in SP3 -- if you're still having problems, please provide a logcat.)
Tethering via wifi.
Phone calls via Bluetooth.
Voice dialing.
Voice search in Google Now. (The app fails to recognize when you stop speaking, so the search is never performed.)
Text-to-speech functionality with Google TTS (Pico TTS works).
Notes:
If the first-run setup keeps crashing on you: from the language selection (first) screen, tap on the four corners of the screen, proceeding clockwise from top left. This will bypass the first-run setup; you can then set up a Google account manually in Settings. (thanks urko95) (If you are still experiencing this with SP4, please report in this thread. A logcat would be helpful.)
Note also that there won't be much in the way of support -- I do have other things that I really should be doing ...
Service Pack 4
Service Pack 4 for the 2012/06/30 SDK JRN83C ROM. This can be flashed on top of the original JRN83C ROM with or without any of the previous service packs applied.
https://docs.google.com/uc?export=download&id=0BwGWbMaI9twWRHFrRUROcDhIeVk http://goo.gl/ZVlQS (many thanks to bl1nkk for hosting) (alternately, check thread for mirrors)
Changes in SP4:
Added the files in /system/usr/srec/en-US from the Nexus 7 JRN84D factory image -- Google Now/voice search, voice dialing, and offline voice dictation input all work.
Added /system/lib/libpatts_engine_jni_api.so from the Nexus 7 JRN84D factory image -- Google TTS now works. (Pico TTS already worked in previous releases.)
Replaced /system/app/SetupWizard.apk with the version from the Galaxy Nexus JRN84D build -- first-run setup should now display properly. (For the curious, I got the apk from Koush's jb-takju.zip and verified that it matched the JRN84D OTA via the SHA1 sums in the OTA update package.)
Added /system/app/{LiveWallpapers,VisualizationWallpapers,HoloSpiralWallpaper}.apk from Nexus S IMM76D to provide some live wallpapers.
Reverted a change in /system/framework/framework-res.apk to the default wallpaper; defaulting to the Nexus live wallpaper hurts performance.
Changes in SP3 (included in SP4):
libhardware_legacy.wifi.so updated to support wifi tethering. (See the linked post for source code.)
Permissions on /system/etc/bluetooth fixed to allow BlueZ to see its config files -- fixes phone calls over a Bluetooth headset, plus lots of other Bluetooth-related functionality.
hwcomposer.s5pc110.so replaced with a build from Jelly Bean-based source -- hopefully fixes hwcomposer bugs people have been experiencing. (See this post for more information.)
Removed /system/app/QuickSearchBox.apk to prevent conflicts with Google Now -- should fix Google Now access for most people. If you're still seeing problems, please provide a full logcat. (thanks afzalarsalan)
Changes in SP2 (included in SP3 and later):
New boot.img with /init.herring.rc edited to fix a thinko which was preventing CPU governor tweak from taking effect -- should result in more smoothness.
/system/build.prop edited to report as a "user" build instead of an "eng" build -- resolves red border flashing on screen. (thanks capez)
/system/etc/media_codecs.xml and /system/etc/media_profiles.xml copied from the Jelly Bean device/samsung/crespo tree -- video recording now works.
/system/lib/libjni_mosaic.so copied from Nexus 7 JRN84D image -- panoramic camera now works.
More changes from Nexus S ICS /system/framework/framework-res.apk integrated -- automatic brightness setting now enabled, tethering menu now enabled (wifi tethering is still broken).
Changes in SP1 (included in SP2 and up):
Jelly Bean audio HAL modules included -- sound now works.
/system/build.prop edited to report as a "user" build instead of an "eng" build -- resolves red border flashing on screen. (thanks capez) I screwed up integrating this fix, so it's not actually part of SP1. Will be in SP2.
/system/bin/make_ext4fs and /system/bin/setup_fs replaced with Nexus 7 JRN84D binaries -- fixes installing apps to SD card. (thanks smojica for reporting)
Removed LegacyCamera app to avoid having two camera apps.
Code:
MD5: ac85b1e309ba3a3f438efe0954c11c32
SHA1: d147f777f8594c5d33dfd480143758107ff1baab
SHA256: 951d39e75e8d4891e18a1da3896567f293074262d8aef3cd0021d4239492cf00
This is safe to flash on top of your ROM, whether or not you have any of the previous service packs installed.
I'll probably continue to distribute updates to this ROM via these service packs, mostly to save everyone bandwidth. (As with MS Windows service packs, they will be cumulative -- e.g. SP5, assuming there is one, will be flashable on top of the base ROM or any of SP1-4.)
FAQ
Frequently Asked Questions:
Did you see that the Jelly Bean source is out?
Yes -- and we're using it to provide audio, among other things. It was faster to use bits and pieces of the source to fix the SDK port than it was to sync and build the whole thing from source -- particularly since Google has not released proprietary blobs matching Jelly Bean for the Nexus S yet.
How do I get root?
The same way you do on a stock ROM -- flash Superuser. (thanks DaxMax)
The first-run setup keeps crashing!
From the language selection (first) screen, tap on the four corners of the screen, proceeding clockwise from top left. This will bypass the first-run setup; you can then set up a Google account manually in Settings. (thanks urko95)
Google Now crashes when I try to use GPS/navigation!
Install Google Maps from Market. (Several of the standard Google apps were not included in the base ROM to save download time.) (thanks legolas93)
My language is something other than US English, and offline speech recognition/voice input doesn't work!
Google's only implemented offline speech recognition for US English at the moment -- all other languages (including other English variants) still rely on Google servers to perform speech recognition.
I can't install the XDA app.
I can't install apps to SD card!
Flash Service Pack 1 or later.
I flashed http://www27.zippyshare.com/v/48676662/file.html, and I still can't install apps to SD card!
Flash Service Pack 1 or later. That zip only includes audio HAL modules and a fix for the red flashes on screen, not the rest of the SP1 bugfixes.
What are those red flashes on screen?
Video recording doesn't work!
Where's the tethering menu?
Flash Service Pack 2 or later.
The bar at the top of the home screen doesn't launch Google Now!
Wifi tethering doesn't work!
My Bluetooth headset/hands-free kit can't be used in phone calls!
Flash Service Pack 3 or later.
Google Now doesn't recognize when I stop talking!
Text-to-speech doesn't work!
Why is "Welcome" in the first-run setup screen so giant?
Flash Service Pack 4 or later.
I flashed 1337kernel, and now XYZ doesn't work!
See this post by Oodie for advice.
XXX/YYY/ZZZ doesn't work!!!!!!
Make sure you've done a full wipe (including data) and flashed the ROM correctly (base ROM, then the latest service pack). Try using the stock kernel included with this ROM; people have reported problems using custom kernels, particularly with sound. If the problem persists, pleave provide a detailed description of the problem and a logcat so that we can help you.
Why not do a full build from source?
This was quicker for me and works quite well. That said, anyone who wants to attempt a build from AOSP and/or CM10 source is welcome to do so, and I'll be happy to answer any questions that may come up in the process.
From the first 30 minutes playing with it.. Google Search / Now takes into account what your saying but doesnt do anything with the data - But doesnt seem to crash with SP1 Also a little big laggy here and there. But pretty much perfect. EXCELLENT ROM Steven676. I have been so excited for this release Thankyou!!
EDIT: Also get a red flash around screen when unlocking phone (still not a huge thing) :]
Looks great, thank you!
So flash the rom, then flash the service pack in op and then service pack in second post?
g1user101 said:
So flash the rom, then flash the service pack in op and then service pack in second post?
Click to expand...
Click to collapse
Both are the same, as I understand
Flashed to SP1 half a day ago and it was rocking! Kudos for this! :good:
I tried flashing GN's JB-SuperSU.zip, it seems to be incompatible (constantly crashing on the permission dialog). Anyone got ideas of how to get root?
nice thread !! i want to try it but i use the Phone calls via Bluetooth on my car radio !! i cant make call when the bluetooth connect on my car radio ?
thanks
thanr said:
Flashed to SP1 half a day ago and it was rocking! Kudos for this! :good:
I tried flashing GN's JB-SuperSU.zip, it seems to be incompatible (constantly crashing on the permission dialog). Anyone got ideas of how to get root?
Click to expand...
Click to collapse
Superuser - Download it and flash it.
DaXmax said:
Superuser - Download it and flash it.
Click to expand...
Click to collapse
Worked
cant bypass the setup screen, tapping 4 corners does nothing? no idea
Bringing over some other tidbits from the other thread about what's broken in SP1:
Automatic brightness setting. I've checked that the ambient light sensor works through another app, so presumably something in the Android framework is missing.
Video recording. Trying to start video recording turns up this set of errors:
Code:
V/videocamera( 2240): startVideoRecording
D/CameraStorage( 2240): External storage state=mounted
V/videocamera( 2240): initializeRecorder
W/StagefrightRecorder( 97): Max file duration is not positive: 0 us. Disabling duration limit.
W/StagefrightRecorder( 97): Target duration (0 us) too short to be respected
V/videocamera( 2240): New video filename: /mnt/sdcard/DCIM/Camera/VID_20120710_025327.mp4.tmp
D/CameraSource( 97): Camera does not support setVideoSize()
E/CameraHardwareSec( 97): Non-metadata buffer mode is not supported!
W/StagefrightRecorder( 97): Failed to create the encoder
D/CameraSource( 97): reset: E
W/CameraService( 97): attempt to use a locked camera from a different process (old pid 97, new pid 2240)
D/CameraSource( 97): reset: X
E/MediaRecorder( 2240): start failed: -2147483648
E/videocamera( 2240): Could not start media recorder.
E/videocamera( 2240): java.lang.RuntimeException: start failed.
E/videocamera( 2240): at android.media.MediaRecorder.start(Native Method)
E/videocamera( 2240): at com.android.camera.VideoCamera.startVideoRecording(VideoCamera.java:1484)
E/videocamera( 2240): at com.android.camera.VideoCamera.onShutterButtonClick(VideoCamera.java:614)
E/videocamera( 2240): at com.android.camera.ShutterButton.performClick(ShutterButton.java:108)
E/videocamera( 2240): at android.view.View$PerformClick.run(View.java:16966)
E/videocamera( 2240): at android.os.Handler.handleCallback(Handler.java:615)
E/videocamera( 2240): at android.os.Handler.dispatchMessage(Handler.java:92)
E/videocamera( 2240): at android.os.Looper.loop(Looper.java:137)
E/videocamera( 2240): at android.app.ActivityThread.main(ActivityThread.java:4745)
E/videocamera( 2240): at java.lang.reflect.Method.invokeNative(Native Method)
E/videocamera( 2240): at java.lang.reflect.Method.invoke(Method.java:511)
E/videocamera( 2240): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:786)
E/videocamera( 2240): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)
E/videocamera( 2240): at dalvik.system.NativeStart.main(Native Method)
V/videocamera( 2240): Releasing media recorder.
V/videocamera( 2240): Empty video file deleted: /mnt/sdcard/DCIM/Camera/VID_20120710_025327.mp4.tmp
This is suggestive of a problem with the video encoding or camera HAL, but replacing libstagefrighthw.so with one built from the Jelly Bean device/samsung/crespo tree doesn't make a difference, and building camera.herring.so from that tree completely breaks the camera app (segfault in a call to libc from camera.herring.so).
There's a thinko in /init.herring.rc which means the tweak to the ondemand CPU governor isn't actually applied.
Lots of reports of Google Now and/or Google Search crashing. A logcat would be helpful for anyone trying to diagnose the problem.
Other notes:
Any ICS kernel should work with this Jelly Bean ROM. People have reported a variety problems with custom kernels. Please make sure you're using the stock kernel before reporting bugs.
That said, it appears that the official release will use a different wireless driver (the bcmdhd driver which Galaxy Nexus already uses), so ICS kernel releases may need some changing for Jelly Bean.
If you're having problems with Market or something else crashing, please provide a logcat -- otherwise problems are difficult to diagnose. Make sure you've wiped all data if you're flashing over an existing ICS installation.
There will be an SP2 to fix the governor issue, along with any other easy wins that crop up, but I'd gently suggest that most further effort should be devoted to a build from source.
figured it out followed this to get past the setup screen:
http://www.youtube.com/watch?v=L5XjF6sPef4
Uploading a version of the port zipaligned and deoxeded... All fixed...
Regards,
Urko
urko95 said:
Uploading a version of the port zipaligned and deoxeded... All fixed...
Regards,
Urko
Click to expand...
Click to collapse
urko what u mean all fixed ??
urko95 said:
Uploading a version of the port zipaligned and deoxeded... All fixed...
Regards,
Urko
Click to expand...
Click to collapse
Can you explain more?
legolas93 said:
Can you explain more?
Click to expand...
Click to collapse
Sorry, I mean that all fixes are applyed, the fixes that Steve realased!
EDIT: Uploading it right now
Regards,
Urko
why is the "ro.build.type" in sp1 still "eng" in stead of "user"?
Hello steven i flashed this port this morning... working very smooth . One problem i have which I'd like to solve. When trying to restore to 4.0.4 cyber or m6 i got md5 mismatch
.. any way i could restore them ? Thank you
Sent from my Nexus S using xda app-developers app
Unofficial CM 10.2 builds for Nexus 4
Hi all,
I decided to post my unofficial builds of CM10.2 for Nexus 4 after being asked by a few people in the CM10.1 Q&A and development threads, in order to consolidate questions and keep clutter down in those threads I decided it was best to make a thread specifically for these builds.
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.3 (Jelly Bean), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. Your changelog is whatever was merged into gerrit.
How to install:
First time installing or coming from another 4.3 based ROM:
Download the ROM
Download a compatible 4.3 Gapps package (I have been using Banks gapps from here: http://forum.xda-developers.com/showthread.php?t=2012857)
Reboot into recovery
Wipe data/Factory reset
Flash the ROM
Flash Gapps
Reboot
Coming from a previous CM10.2 nightly:
Download the ROM
Reboot into recovery
Flash the ROM
Reboot
Coming from a previous CM10.1 nightly:
Download the ROM
Download a compatible 4.3 Gapps package (I have been using Banks gapps from here: http://forum.xda-developers.com/showthread.php?t=2012857)
Reboot into recovery
Flash the ROM
Flash Gapps
Reboot
Builds:
Built from official CM sources only, no cherry-picks, no changes, no additions. I will not be changing the official sources in any way so don't bother asking.
http://goo.im/devs/thracemerin/cm_builds/mako
Note: These builds are produced by my buildbot at 4am US Eastern time (build + upload takes approximately 90 minutes), the repo will be synced during the build process to ensure that the latest sources are used. The completed file size should be approximately 196MB, so if the latest download isn't it's not fully uploaded yet
Note 2: If the build fails for some reason, I will try to build one later in the day, but if I can't you may have to wait until the following day.
How to get root:
In order to get root access, you need to do the following:
Activate the Developer Settings by going to Settings->About Phone ant tap on the Build Number 7 times.
Go to Settings->Developer Options and change the Root Access to 'Apps and ADB'
You may also need to activate USB Debugging in Developer Options (some people say you do, others say you don't)
Note: If you have flashed a kernel that comes with it's own boot.img package it may not have the correct instructions to start the internal su daemon as a result root will stop working, at the moment the best way to fix this is to not use that kernel. If you absolutely have to use a custom kernel you may need to flash SuperSU for the moment or ask your kernel dev to support this feature.
Known Issues
None that I'm aware of, but keep in mind that these are pre-nightly builds and could contain bugs and/or non-working features at any time.
Thanks
Google
CyanogenMod
F.A.Q
Q: When will official builds start?
A: Soon
CyanogenMod Blog said:
“Who cares about the old, gimme 10.2!”
We have one last internal item on our checklist before we open the floodgates on CM 10.2 nightlies. We fell into an old habit in 10.1 and the settings menu became more cluttered than we would like, and at times confusing both in presentation and in code. We are working to resolve this before 10.2 nightlies begin, so the transition is less jarring than it would down the line. Expect the new layout to be in effect with the first nightlies. If all goes well, we are talking days, not weeks.
In the meantime, the majority of our 10.1 roster have transitioned to being 10.2 capable. This means for you at-home builders, things should be in a fairly good spot for your own personal builds. If you want to checkout all the stuff we’ve merged, click through the pages.
Click to expand...
Click to collapse
Q: What is SELinux?
A:
CyanogenMod Blog said:
What is SELinux?
The project’s official description reads “SELinux is a security enhancement to Linux which allows users and administrators more control over access control.”
SELinux is a set of Open sourced and peer reviewed changes to the core Android Software stack to help prevent apps from performing malicious activities. This is done by establishing a set of policies that act as mandatory access controls (MAC). Depending on the policy, it can do things such as prevent apps from running or accessing specific data, to preventing root access altogether.
SELinux has wide-scale adoption throughout the linux landscape, with Fedora, Red Hat and others incorporating policies to better the system security. The default policies are usually written per distribution, by their maintainers – we have begun this process for CyanogenMod.
We will be working on this policy creation in parallel to Google’s own policies for Android, which we believe will be released with the Android 4.3 source; effectively getting us ahead of the eventual 4.3 source release. As this process is open source, policy creation and suggestions will be handled via our gerrit instance.
What it’s not?
SELinux is not a backdoor for government agencies to spy on you. It is not PRISM, PROMIS, CARNIVORE, The Great Firewall or any other ominous Big Brother-like initiative.
Access Control Modes
By default, we will be shipping with SELinux capabilities enabled in the kernel, but in a Permissive mode. What this means is that your phone will behave exactly as it currently does, with no noticeable change to the user.
There are 3 modes in total, Enforcing, Permissive and Disabled. While in Enforcing mode, SELinux policies are enforced, preventing whatever causes a violation (ie su). Permissive mode logs policy violations, but does not prevent the activity that caused it. Disabled turns SELinux off.
We are using Permissive mode as our default so we can come up with sensible policies. If you submit a log for us to analyze (via JIRA) for SELinux policy improvements, the logged exceptions will be of high value.
This will be an ongoing process as we work to incorporate sensible policies for each device repo. As always our source is available on Github and patches will be peer reviewed via gerrit. For those more attuned to personal data security, you are welcome to watch and audit our efforts. For the rest of you, sit back and relax – no need for pitchforks.
Click to expand...
Click to collapse
Third
amazing mate, keep it up the good work!
Hey, thanks for the builds. Do you have any idea in your great widsom as to why the various Gapps packages vary in size to such a great extent?
First, we have Banks, which is extremely minimalist, at least when compared to official 10.1 Gapps.
Then, we have a 10.2 un-authored Gapps package, often linked in the CM discussion, which is about the size of the official 10.1 one, but seems to require Banks's photosphere add-on.
Lastly we have doomed's version which approaches a whopping 200 MBs.
What on earth can account for such varying sizes, and as the purist that I think you are, why do you use the minimalist Banks Gapps?
Feedback
Nice man, thanks for this work, btw, the front cam is upside down.
floepie said:
Hey, thanks for the builds. Do you have any idea in your great widsom as to why the various Gapps packages vary in size to such a great extent?
First, we have Banks, which is extremely minimalist, at least when compared to official 10.1 Gapps.
Then, we have a 10.2 un-authored Gapps package, often linked in the CM discussion, which is about the size of the official 10.1 one, but seems to require Banks's photosphere add-on.
Lastly we have doomed's version which approaches a whopping 200 MBs.
What on earth can account for such varying sizes, and as the purist that I think you are, why do you use the minimalist Banks Gapps?
Click to expand...
Click to collapse
BaNkS only includes the essential Google Apps that are needed for the Google experience -- working sync services, the Play Store itself, and so on. He provides other Google Apps in the form of an add-on, a separate zip, for the keyboard/camera/etc. Basically, most of the Google Apps are now available to download from the store itself (Keep, Earth, Maps, Voice Search, Search and so on). That wasn't always the case, but still some are releasing a full Google Apps package with everything.
The minimalistic approach is obvious - only install what is necessary, manually get anything else yourself. That is why the banks package is small because it is not forcing other apps that people may or may not use since they could simply download it themselves if they wanted to. I assume the 200mb or more package is simply every single Google APK that comes with the official factory images.
lwkkazz said:
Nice man, thanks for this work, btw, the front cam is upside down.
Click to expand...
Click to collapse
Weird, doesn't seem to be for me.
floepie said:
Hey, thanks for the builds. Do you have any idea in your great widsom as to why the various Gapps packages vary in size to such a great extent?
First, we have Banks, which is extremely minimalist, at least when compared to official 10.1 Gapps.
Then, we have a 10.2 un-authored Gapps package, often linked in the CM discussion, which is about the size of the official 10.1 one, but seems to require Banks's photosphere add-on.
Lastly we have doomed's version which approaches a whopping 200 MBs.
What on earth can account for such varying sizes, and as the purist that I think you are, why do you use the minimalist Banks Gapps?
Click to expand...
Click to collapse
markd0wn basically covered it, but it also depends on what you want in your /system directory, most of the apps that used to come in Gapps packages are now available in the Play Store as stand alone packages so you can still get them if you want them and they get installed as user apps instead of system apps, not that it makes a tremendous difference, but for the most part they don't need to be in /system.
thracemerin said:
Weird, doesn't seem to be for me.
Click to expand...
Click to collapse
It's ok now , Hey man, it is normal that the ROM occupy 4Gb of the memory? (I'm new to Nexus 4, I get my yesterday haha)
lwkkazz said:
It's ok now , Hey man, it is normal that the ROM occupy 4Gb of the memory? (I'm new to Nexus 4, I get my yesterday haha)
Click to expand...
Click to collapse
Android reserves around 4GB of the total space on the device. Yes, it is quite normal.
Glad I picked up the 16GB model.
thracemerin said:
Weird, doesn't seem to be for me.
Click to expand...
Click to collapse
My front facing cam is upside down using focal, but in the stock app its fine
Sent from my Nexus 4 using Tapatalk 4
l.m.prowse said:
My front facing cam is upside down using focal, but in the stock app its fine
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Hmm....it's early for focal still, probably just an oddity.
@thracemerin, any way to know if the CM team are aware of the homescreen shortcut bug? maybe I should search JIRA for it... since I'm not sure they follow all threads here. Doesn't seem to happen to everyone though. Happens to me in every unofficial 10.2 build (gonna try yours now after full wipe). The only thing I'm changing is the number of homescreens from the default of 5 to less (for example 2). After that, it's very easy to reproduce - simply add a few apps from the drawer to the homescreen, also put some apps in folders, then reboot, and you'll see what I'm talking about (in case you don't already know). It also happens randomly without reboots, maybe when Trebuchet is refreshing itself or something, but reboot forces it to happen quicker.
markd0wn said:
@thracemerin, any way to know if the CM team are aware of the homescreen shortcut bug? maybe I should search JIRA for it... since I'm not sure they follow all threads here. Doesn't seem to happen to everyone though. Happens to me in every unofficial 10.2 build (gonna try yours now after full wipe). The only thing I'm changing is the number of homescreens from the default of 5 to less (for example 2). After that, it's very easy to reproduce - simply add a few apps from the drawer to the homescreen, also put some apps in folders, then reboot, and you'll see what I'm talking about (in case you don't already know). It also happens randomly without reboots, maybe when Trebuchet is refreshing itself or something, but reboot forces it to happen quicker.
Click to expand...
Click to collapse
I heard about it, but I always use Apex Launcher so it doesn't happen to me. I'm not sure they want you to put things for 10.2 on JIRA or not (probably not) but its a fairly serious thing, so you could try logging it, worst case they ignore it.
thanks for posting this thracemerin. I've started my own builds (mostly for fun, to see if I could!), but I wanted to try some known good 4.2 builds before I flash one of my own. Your build and instructions are great. It's running smooth except for two things:
- I can't get my titanium backups to restore user apps, it just hangs at 0%. No big deal, I've just been installing from play store manually.
- Installing swype gives an error -24 . I did a clean install of your CM build, so data was wiped; there is nothing from nuance in data/data to wipe. This may or may not be related to the error with TiBu because it also was trying to install swype from a backup. I guess I'll play with the stock keyboard for a while.
thanks again.
nighthawkca said:
thanks for posting this thracemerin. I've started my own builds (mostly for fun, to see if I could!), but I wanted to try some known good 4.2 builds before I flash one of my own. Your build and instructions are great. It's running smooth except for two things:
- I can't get my titanium backups to restore user apps, it just hangs at 0%. No big deal, I've just been installing from play store manually.
- Installing swype gives an error -24 . I did a clean install of your CM build, so data was wiped; there is nothing from nuance in data/data to wipe. This may or may not be related to the error with TiBu because it also was trying to install swype from a backup. I guess I'll play with the stock keyboard for a while.
thanks again.
Click to expand...
Click to collapse
For the titanium backup problem, I switched the backup folder to the legacy selection in the preference menu and was then able to restore. Hope that helps
Sent from my Nexus 4 using xda premium
nighthawkca said:
thanks for posting this thracemerin. I've started my own builds (mostly for fun, to see if I could!), but I wanted to try some known good 4.2 builds before I flash one of my own. Your build and instructions are great. It's running smooth except for two things:
- I can't get my titanium backups to restore user apps, it just hangs at 0%. No big deal, I've just been installing from play store manually.
- Installing swype gives an error -24 . I did a clean install of your CM build, so data was wiped; there is nothing from nuance in data/data to wipe. This may or may not be related to the error with TiBu because it also was trying to install swype from a backup. I guess I'll play with the stock keyboard for a while.
thanks again.
Click to expand...
Click to collapse
Thanks to DJLamontagneIII for this:
Titanium backup Users
1. In tb go to menu>preferences>backup folder location
2. Navigate to storage/emulated/legacy
3. Select your Backup folder and Select "Use the current folder"
4. Then it will ask you to move backup to that folder.... Select that
5. Restart app and restore.
jpreichart said:
For the titanium backup problem, I switched the backup folder to the legacy selection in the preference menu and was then able to restore. Hope that helps
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Beat me to it
Another bug that I think is introduced in the 08-11 build is lockscreen slider shortcuts not saving (but if you changed them on a previous build and updated to 08-11, they'd probably be set up right).
I managed to save them anyway using a workaround. Basically setting them all as 'Empty' and hitting the save button won't do - you'd turn screen off/on and it will still have the default ones. What I did to 'fix' this is set each one to empty and tap save inbetween changing each one, then tap save again after they're all empty, then I tapped the icon that restores all to default, suddenly the 'default' is what I just set up (all empty), then hit save again, and voila, saved successfully. Could probably skip a few of those steps that I did as I'm sure one of them did the trick and the others were just me testing, but at least it works.
Another thing that confirms that they're changing something related to lockscreen shortcuts, is that after achieving this, the lockscreen is now stock-style-behavior. Before, when you set all shortcuts to empty, pressing and holding the lock icon would let you drag it to each spot that became empty but it still appeared as an "empty shortcut". Now, you don't see the spots where shortcuts would normally be, it's just all a circle.
(I'm reporting all of this just in case it helps someone )
markd0wn said:
Another bug that I think is introduced in the 08-11 build is lockscreen slider shortcuts not saving (but if you changed them on a previous build and updated to 08-11, they'd probably be set up right).
I managed to save them anyway using a workaround. Basically setting them all as 'Empty' and hitting the save button won't do - you'd turn screen off/on and it will still have the default ones. What I did to 'fix' this is set each one to empty and tap save inbetween changing each one, then tap save again after they're all empty, then I tapped the icon that restores all to default, suddenly the 'default' is what I just set up (all empty), then hit save again, and voila, saved successfully. Could probably skip a few of those steps that I did as I'm sure one of them did the trick and the others were just me testing, but at least it works.
Another thing that confirms that they're changing something related to lockscreen shortcuts, is that after achieving this, the lockscreen is now stock-style-behavior. Before, when you set all shortcuts to empty, pressing and holding the lock icon would let you drag it to each spot that became empty but it still appeared as an "empty shortcut". Now, you don't see the spots where shortcuts would normally be, it's just all a circle.
(I'm reporting all of this just in case it helps someone )
Click to expand...
Click to collapse
They're doing a fairly significant reworking of the entire settings apk and all of the CyanogenMod settings, it's possible something got added/removed that broke this temporarily. I would expect that certain settings menus, etc... may be broken over the next little while before the official nightlies begin.
Apologies for the links: as I am a new user, I am not allowed to directly link to outside sources. Please replace _ with :// or . (Forum suggestion: use optional pre-publication review for posts from new users that depend strongly on external links.)
INTRODUCTION: My BMW 318 (E46, 2004) had a factory default BMW ULF bluetooth module (early generation) that worked fine with my BB Q10 and all phones up to Android 4.1. From 4.2 onwards, I and many others have been having problems with keeping the Bluetooth connection alive for more than a few seconds. This has been widely reported but never addressed in stock Android. As even the latest OTA upgrade to 4.4.3 didn't solve it, I decided to compile the required Bluetooth kernel module myself.
BACKGROUND: The change from the Bluez to Bluedroid system in Android 4.2 caused the compatibility issues. User 'wulu' at the forums of CyanogenMod reported on how he patched his CM10.2 (and later) to include a patch that solves the issue. I repeated his procedure for stock 4.4.3 for the Nexus 5.
Markus Schmidt's problem description & patch: https_github_com/Root-Box/external_bluetooth_bluedroid/commit/97d2f6346bad56299f60cfcd8c45ad893a0da78c
Wulu's specifics for Nexus 5 & BMW's ULF for CM: http_forum_cyanogenmod_com/topic/77834-bluetooth-connection-drops-car-kit-bmw/
METHODS:
The following procedure is specifically to compiled the Bluetooth kernel module for the Nexus 5 hardware and the 4.4.3_r1.1 (OTA) release. It should therefore only work for this specific combination. If you want to compile the module yourself, please read the linked pages with Google's excellent instructions: http_source_android_com/source/initializing.html
Here are a couple of notes I made that deal with some specifics for my Mac and the Nexus 5:
On Mountain Lion (Mac), I had to use Xcode 5.0.2 to get past a compile error. See instructions here on how to download and use the older 5.0.2 version of Xcode: https_groups_google_com/forum/#!topic/android-building/FPCSo1xKJ4U
Do not download the "master" source using the repo command, but download "android-4.4.3_r1.1". The master source has post-OTA changes that make a compiled module incompatible with the OTA release for the Nexus 5. "android-4.4.3_r1.1" was listed on those pages as specifically the version that was used for the OTA 4.4.3 upgrade for the Nexus 5.
Setup the environment as instructed and add the three proprietary driver sets listed for the Nexus 5 and 4.4.3 (see "Building for devices" on the Google pages).
There is no need to use the full patch. You can make the two small modifications to the bta_ag_sdp.c file using any text editor. Find the file first (find . -name "bta_ag_sdp.c") and commend out the two lines with the minus signs given in wulu's the first post (or Markus Schmidt's patch) by putting a # in front of both lines: #if (p_scb->peer_features == 0), #p_scb->peer_features = p_attr->attr_value.v.u16;.
Select the "aosp_hammerhead-userdebug" (=Nexus 5) option with the lunch command, and compile using the make command. I was able to follow the instructions pretty much to the letter without any problems.
After the compilation I had two version of the file, in four locations. They are easily found using the find command (find . -name "bluetooth.default.so" -exec ls -la {} \. The bigger one (in the symbols subdirectory) is for debugging. The smaller one is the one I used (and which is linked in this message). It was located at "./out/target/product/hammerhead/system/lib/hw/bluetooth.default.so" in my source tree.
After this, it was pretty straightforward. I rooted my Nexus 5, re-installed FX (with paid-for Root add-on, but the free ES File Explorer should also work), uploaded the file via Dropbox and its Save to SD, transferred it to the R/W mounted system directory to replace /system/lib/hw/bluetooth.default.so with it, and restarted my phone. I also modified the config file (/system/etc/bluetooth/auto_pair_devlist.conf) that blacklists BMW components by commenting out most lines, but I am not sure if this is helpful or not.
RESULTS: It seems a little bit less stable than the Bluetooth connection I had with my Blackberry, but it definitely works. I was able to transfer my contacts and to make and receive calls. For anybody with stock KitKat 4.4.3 on the Nexus 5, here is the bluetooth.default.so kernel module: http_s000_tinyupload_com/index.php?file_id=07750725920558658087
DISCUSSION: The compilation procedure can undoubtedly be optimized. I compiled the entire source tree over several hours, just to be sure I didn't miss out on things. Feel free to give tips, but I'm happy that it worked at all.
CONCLUSION: Thanks to wulu's advice in the CM forum thread I was able to compile a patched Bluetooth module for stock Android with KitKat 4.4.3 that works with my BMW 318 (E46, 2004) ULF car kit.
That´s great! :good:
Is it possible for you to provide the same for Nexus 5 - 4.4.4 OTA ?
mnasty said:
That´s great! :good:
Is it possible for you to provide the same for Nexus 5 - 4.4.4 OTA ?
Click to expand...
Click to collapse
Yes, great job!
Nobody have already done this for 4.4.4 ? I'll do this if I have time.
ZeroKcm said:
Yes, great job!
Nobody have already done this for 4.4.4 ? I'll do this if I have time.
Click to expand...
Click to collapse
4.4.4 from 4.4.3 is only security fixes, everything else is the same.
Does 5.0 Lollipop resolve the BMW ULF connection issue?
guys, do you think 5.0 Lollipop would resolve the current BMW ULF connection problem? Have anyone tried the 5.0 yet ?
I'm still in 4.4.3 working great on N5 paring ULF 8th Gen kit, thanks for S1010, wulu and Alpejohn guiding me the entire process.
REV HRD said:
guys, do you think 5.0 Lollipop would resolve the current BMW ULF connection problem? Have anyone tried the 5.0 yet ?
I'm still in 4.4.3 working great on N5 paring ULF 8th Gen kit, thanks for S1010, wulu and Alpejohn guiding me the entire process.
Click to expand...
Click to collapse
I have the same disconnect issue with my Seat, haven't tried the fix cause I was running 4.4.4 and there was no ready module for it, but lollipop didn't fixed it. I tried compilation without success. I followed all the instructions and compiled it successfully, but after replacing it, bluetooth fails to start. In the logcat logs I can see that it complains there is no bluetooth (something like that, don't have the exact logs to check it now), seems the compiled so file is not compatible.
If anyone can give a hand on this
Not sure if Seat using the same implementation as BMW ULF kit provides, my family also has a 06 Audi A4 with stock BT, I don't experience any connection issue from the stock 4.4.3 on N5. I would think Audi / Seat might use the same BT module as they share most of the VW parts.
I experience the same disconnects. I was experiencing it and with the old phone Galaxy Nexus, till one day I updated to cyanogenmod and the problem was gone. Then changed the phone with Nexus5 and again I have the same issues, tried everything with no luck. Changing the kernel, doing some stuff with paid bluetooth apps to manage the phonebook that the car is accessing. So I suspect the problem is the same
(Seems I'm still not able to post links, I just prepared one with the Blutooth device model number and year on it, if it mean anything to someone it is from 03.2007).
Don't work in lollipop, in your free time please compile a new file.
Thks.
S1010 said:
Apologies for the links: as I am a new user, I am not allowed to directly link to outside sources. Please replace _ with :// or . (Forum suggestion: use optional pre-publication review for posts from new users that depend strongly on external links.)
INTRODUCTION: My BMW 318 (E46, 2004) had a factory default BMW ULF bluetooth module (early generation) that worked fine with my BB Q10 and all phones up to Android 4.1. From 4.2 onwards, I and many others have been having problems with keeping the Bluetooth connection alive for more than a few seconds. This has been widely reported but never addressed in stock Android. As even the latest OTA upgrade to 4.4.3 didn't solve it, I decided to compile the required Bluetooth kernel module myself.
BACKGROUND: The change from the Bluez to Bluedroid system in Android 4.2 caused the compatibility issues. User 'wulu' at the forums of CyanogenMod reported on how he patched his CM10.2 (and later) to include a patch that solves the issue. I repeated his procedure for stock 4.4.3 for the Nexus 5.
Markus Schmidt's problem description & patch: https_github_com/Root-Box/external_bluetooth_bluedroid/commit/97d2f6346bad56299f60cfcd8c45ad893a0da78c
Wulu's specifics for Nexus 5 & BMW's ULF for CM: http_forum_cyanogenmod_com/topic/77834-bluetooth-connection-drops-car-kit-bmw/
METHODS:
The following procedure is specifically to compiled the Bluetooth kernel module for the Nexus 5 hardware and the 4.4.3_r1.1 (OTA) release. It should therefore only work for this specific combination. If you want to compile the module yourself, please read the linked pages with Google's excellent instructions: http_source_android_com/source/initializing.html
Here are a couple of notes I made that deal with some specifics for my Mac and the Nexus 5:
On Mountain Lion (Mac), I had to use Xcode 5.0.2 to get past a compile error. See instructions here on how to download and use the older 5.0.2 version of Xcode: https_groups_google_com/forum/#!topic/android-building/FPCSo1xKJ4U
Do not download the "master" source using the repo command, but download "android-4.4.3_r1.1". The master source has post-OTA changes that make a compiled module incompatible with the OTA release for the Nexus 5. "android-4.4.3_r1.1" was listed on those pages as specifically the version that was used for the OTA 4.4.3 upgrade for the Nexus 5.
Setup the environment as instructed and add the three proprietary driver sets listed for the Nexus 5 and 4.4.3 (see "Building for devices" on the Google pages).
There is no need to use the full patch. You can make the two small modifications to the bta_ag_sdp.c file using any text editor. Find the file first (find . -name "bta_ag_sdp.c") and commend out the two lines with the minus signs given in wulu's the first post (or Markus Schmidt's patch) by putting a # in front of both lines: #if (p_scb->peer_features == 0), #p_scb->peer_features = p_attr->attr_value.v.u16;.
Select the "aosp_hammerhead-userdebug" (=Nexus 5) option with the lunch command, and compile using the make command. I was able to follow the instructions pretty much to the letter without any problems.
After the compilation I had two version of the file, in four locations. They are easily found using the find command (find . -name "bluetooth.default.so" -exec ls -la {} \. The bigger one (in the symbols subdirectory) is for debugging. The smaller one is the one I used (and which is linked in this message). It was located at "./out/target/product/hammerhead/system/lib/hw/bluetooth.default.so" in my source tree.
After this, it was pretty straightforward. I rooted my Nexus 5, re-installed FX (with paid-for Root add-on, but the free ES File Explorer should also work), uploaded the file via Dropbox and its Save to SD, transferred it to the R/W mounted system directory to replace /system/lib/hw/bluetooth.default.so with it, and restarted my phone. I also modified the config file (/system/etc/bluetooth/auto_pair_devlist.conf) that blacklists BMW components by commenting out most lines, but I am not sure if this is helpful or not.
RESULTS: It seems a little bit less stable than the Bluetooth connection I had with my Blackberry, but it definitely works. I was able to transfer my contacts and to make and receive calls. For anybody with stock KitKat 4.4.3 on the Nexus 5, here is the bluetooth.default.so kernel module: http_s000_tinyupload_com/index.php?file_id=07750725920558658087
DISCUSSION: The compilation procedure can undoubtedly be optimized. I compiled the entire source tree over several hours, just to be sure I didn't miss out on things. Feel free to give tips, but I'm happy that it worked at all.
CONCLUSION: Thanks to wulu's advice in the CM forum thread I was able to compile a patched Bluetooth module for stock Android with KitKat 4.4.3 that works with my BMW 318 (E46, 2004) ULF car kit.
Click to expand...
Click to collapse
FYI, had similar issue with 2009 E61 5 series. Solution was third party app (Bluetooth Phone book) and a full software update for the car from the dealer. The app cost a few quid, the dealer software update much more!
That said, it works perfectly with stock Lollipop and I consider it money well spent.
---------- Post added at 09:15 PM ---------- Previous post was at 09:13 PM ----------
FYI, it was this app: https://play.google.com/store/apps/details?id=com.android_rsap.irmc
CottonmouthOS
A security and privacy focused mobile operating system based on CopperheadOS that is MicroG friendly.
Code:
DISCLAIMER: NOT RESPONSIBLE FOR BROKEN PHONES OR LIVES
This ROM is based on the great CopperheadOS ROM with signature spoofing enabled to allow MicroG framework. There will be changes to make the signature spoofing spoof ONLY the Google service signatures and ONLY usable/allowable by MicroG services ONLY. The new name CottonmouthOS is a way to distinguish from CopperheadOS builds, because of the signature spoofing patches.
Prerequisites coming from other ROMs :-
Have latest March factory image installed.
Instructions :-
Download the CottonmouthOS ROM
Follow the install guide
Have a more private and secure phone
Features :-
Features of CopperheadOS ROM
Note :-
CottonmouthOS is meant to be used with the bootloader locked with NO custom recovery installed and no GAPPS.
Credits :-
CopperheadOS team
Mar-V-in for MicroG
razorloves for inspiration
References :-
Copperhead homepage
Documentation
Instructions used to build
Sources
MicroG patch
If anyone wants to reupload to a better file hosting site please do.
OLD OP
CopperheadOS
A security and privacy focused mobile operating system compatible with Android apps
Code:
DISCLAIMER: NOT RESPONSIBLE FOR BROKEN PHONES OR LIVES
CopperheadOS - a hardened FOSS operating system based on the Android mobile platform. Its based on Android Open Source Project with added privacy and security features.
Prerequisites :-
Have latest factory image installed
Instructions :-
Download the UNOFFICIAL CopperheadOS ROM
- Mirror 1
- Mirror 2
- Mirror 3
Follow the install guide
Have a more private and secure phone
Features :-
Protection from zero-days
Prevents many vulnerabilities and makes exploits harder
Hardened C standard library and compiler toolchain
Catches memory corruption and integer overflows
Hardened kernel
Kernel self-protection and high quality ASLR
Stronger sandboxing and isolation for apps & services
Stricter SELinux policies, seccomp-bpf and more
Backported security features and quicker patching
Benefiting from upstream changes long before stock
Firewall & network hardening
Along with improvements like MAC randomization
Open-source and free of proprietary services
Uses alternatives to Google apps/services like F-Droid
Security-centric user experience changes
Better defaults, finer-grained permission control
Note :-
Copperhead is meant to be used with the bootloader locked with NO custom recovery installed and no GAPPS.
Credits :-
CopperheadOS team and razorloves for inspiration.
References :-
Copperhead homepage
Documentation
Instructions used to build
Last Updated 2018-02-28
Does copperhead have the pixel navbar animation?
File not yet uploaded
ChongoDroid said:
File not yet uploaded
Click to expand...
Click to collapse
+1
ChongoDroid said:
File not yet uploaded
Click to expand...
Click to collapse
That is strange. Will reupload.
EDIT: Done see OP
I've always wondered something, since COS charges money for phone flashing and the only way to get it yourself is to compile it yourself and flash. Once you flash your self compiled build, do you have to build the updates or does the built in updater work?
ChongoDroid said:
I've always wondered something, since COS charges money for phone flashing and the only way to get it yourself is to compile it yourself and flash. Once you flash your self compiled build, do you have to build the updates or does the built in updater work?
Click to expand...
Click to collapse
I didn't see the updater, and even if it was there the keys would not match so you would not be able to update.
Ideally, we would put this on a build server and release the full install and OTA every time there was an update so we would get the updates within a few hours of official. A few changes could be made to either change the updater (if it is there, which I did not see it) or use lineageOS one and modify it to point to the release server.
jahrule said:
I didn't see the updater, and even if it was there the keys would not match so you would not be able to update.
Ideally, we would put this on a build server and release the full install and OTA every time there was an update so we would get the updates within a few hours of official. A few changes could be made to either change the updater (if it is there, which I did not see it) or use lineageOS one and modify it to point to the release server.
Click to expand...
Click to collapse
Yeah CopperheadOS uses the stock recovery iirc. They do it like this to use verified boot iirc. I personally loved COS on my Nexus 5 and missed it on my pixel.
how likely are weekly builds for this rom? also did you find a workaround for the F-Droid extension? I tried manually removing it and disabling it via twrp, but it seems to restore itself or simply refuse to delete, showing as deleted from within twrp
Thank you for building this, I tried and failed miserably. Will flash it today :good:
Fdroid Keys and BuildSystem
Thanks for building.
Please add your keys to the fdroid whitelist.
Could you write/post about your build system?(Like a Howto)?
KShion619 said:
how likely are weekly builds for this rom? also did you find a workaround for the F-Droid extension? I tried manually removing it and disabling it via twrp, but it seems to restore itself or simply refuse to delete, showing as deleted from within twrp
Click to expand...
Click to collapse
The fdroid extension needs the keys as I pointed out in the 2nd or 3rd post notes. Regular builds would require a build server but a build server costs money. So, will try to update when I can.
smilingtux said:
Thanks for building.
Please add your keys to the fdroid whitelist.
Could you write/post about your build system?(Like a Howto)?
Click to expand...
Click to collapse
Please see the build instructions in the op that I posted.
Ideally, I would like to make another rom that has the restricted sigspoof added so we could have an option for microg
jahrule said:
The fdroid extension needs the keys as I pointed out in the 2nd or 3rd post notes. Regular builds would require a build server but a build server costs money. So, will try to update when I can.
Click to expand...
Click to collapse
Meant like a user-doable way until the keys updated, I'm fine with the full screen dialog for now
KShion619 said:
Meant like a user-doable way until the keys updated, I'm fine with the full screen dialog for now
Click to expand...
Click to collapse
The keys are compiled in so, no.
jahrule said:
Please see the build instructions in the op that I posted.
Click to expand...
Click to collapse
I have seen and read it before
I setup an build host based on copperheads documentation, I read about the java whitelisting of my keys for fdroid, but the build process itself fails from time to time.
So my question was more about, how did you manage to setup a reliable environment for building. What OS did you use, installed dependencies etc.
smilingtux said:
I have seen and read it before
I setup an build host based on copperheads documentation, I read about the java whitelisting of my keys for fdroid, but the build process itself fails from time to time.
So my question was more about, how did you manage to setup a reliable environment for building. What OS did you use, installed dependencies etc.
Click to expand...
Click to collapse
You seem to ask for a docker.
LineageOS 18.1 UNOFFICIAL for 2015 Samsung Galaxy Tab S2 SM-T715 ONLYModel: SM-T715 (LTE) - gts28ltexx - 8" screen, Exynos 5433 SoC, LTE
This is the ONLY model that the ROM will work on.
There is NO ROM for the T710, T810 or T815 in this thread. Questions about T710, T810 or T815 will be completely IGNORED.
For T710 please use the equivalent ROM at its separate XDA forum thread.
For T810 please use the equivalent ROM at its separate XDA forum thread.
You MUST READ posts 1-3 (about 10 minute read) before deciding to install this ROM. If you think this is an unreasonable request, then stop reading now and find another ROM. Thank you.
DISCLAIMER
I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this ROM.
All involved in bringing this build to you are working voluntarily on it in very limited spare time, and their other life commitments have much higher priority. Don't expect a prompt, or even any, response to questions and bug reports.
Before attempting to install this ROM
1. Ask yourself: would bricking your device be a disaster for you? If yes, don't try this ROM! It can't be guaranteed stable and reliable enough to depend on for daily use.
2. BACKUP YOUR DATA AND EXISTING ROM. Be prepared for a complete restore if anything goes wrong.
3. RESEARCH adb, fastboot, Odin/heimdall, and TWRP and how to use them, if not already familiar with these.
What works
bluetooth
wifi
GPS
brightness
audio through loudspeaker
audio through headphone jack
audio over bluetooth
SELinux enforcing
DRM level 3 (SD definition)
deep sleep
RIL - mobile data and telephony/SMS/Cell Broadcast - some limitations for telephony audio options apply, see below
vibration and haptic feedback
hardware buttons and lighting
What doesn't work
fingerprint. As retiredtab wrote in post 1891 at
https://forum.xda-developers.com/t/...t810-t815-t815y.3879302/page-95#post-85533725
the team will not spend anymore time looking at fingerprint. If you need fingerprint to work, stay with stock Samsung ROM.
DRM level 1 (no HD definition). There's more detail in post 1891 above. I will not be trying to achieve level 1 for HD definition. If you need HD definition for your streaming media, stay with stock Samsung ROM.
If you charge the device while it's powered off and then want to power it on, you MUST wait at least 30 seconds AFTER disconnecting the charger cable before pressing the power button otherwise you might run into strange boot problems such as the touch screen not working. While recent builds solved the touchscreen issue, you still might see excessive battery drain until you perform another reboot.
For telephony audio, currently only the loudspeaker option is working. If you try to use/switch to bluetooth audio during a phone call, the audio stack will go wild and afterwards loudspeaker will stop working too until you perform a reboot.
Please note that for an incoming call, it might take a couple of seconds until both sides can hear each other.
I have invested a lot of time trying to troubleshoot the audio routing, and this is for sure a device-specific issue most likely due to the the old Samsung binaries so chances are almost zero to get that fixed.
Possibly other features that I haven't tested or do not use.
Source Code
See FAQ 1 for links in post #2.
Thanks
LineageOS team for the upstream source code.
@retiredtab, @ananjaser1211, @lpedia, @Yogi555 and @CuckooPenguin for spending nearing 1 month fixing the 2 most biggest bugs in 17.1 that plagued users for nearly 10 months: the wifi instability and random reboots. These are discussed in detail at
https://forum.xda-developers.com/t/...rs-running-any-version-of-android-10.4308193/
https://forum.xda-developers.com/t/...rs-running-any-version-of-android-10.4308203/
A special shout out to retiredtab for providing the T710 ROM and code here which is the base for this ROM. Also this ROM would not have been possible with all the help and mentoring he provided during the past 6 months of development. Also many thanks to lpedia and bluess57 for their outstanding hints and tips.
All past contributors of the exynos5433 code, especially ananjaser1211 for his major contributions and @ripee for working on prior gts2 builds until end of 2021.
@rINanDO for his lmkd spam fix in 18.1.
Alpha testers: simon-edwards for the many hours testing and helping troubleshooting RIL, SELinux policies and various gapps options; Don K and Sir Thopas for addional RIL model testing.
@bluess57 for his excellent code donations for the gts2 LTE models.
retiredtab and lpedia for providing the blueprint for this forum entry and the FAQ in post #2 and constantly improving it. This work is just a little contribution standing on strong shoulders of previous contributions.
Frequently Asked Questions. You MUST READ this before posting any questions. Thank you.
QuestionAnswerQ1. Can I build this ROM for myself? Where are the source and kernel source files?A1. Yes, you can. The source files are listed below.
Kernel
https://github.com/metterschlg/android_kernel_samsung_universal5433
Device Tree
https://github.com/metterschlg/android_device_samsung_gts2-common-selinux
https://github.com/metterschlg/android_device_samsung_gts28ltexx
Vendor
https://github.com/metterschlg/proprietary_vendor_samsung
In addition, there is a repo diff file for device-specific tweaks needed to work and a roomservice.xml (local manifest file) file so you can build this rom yourself. The other patch required for tcp/ip is at https://github.com/DerpFest-11/pack...mmit/22fd53a977eeaf4e36be7bf6358ecf2c2737fa5e
Build manifest can be found at
https://github.com/metterschlg/local_manifests/blob/lineage-18.1/gts28ltexx.xml
Build environment setup is docmented (as code) at
https://github.com/metterschlg/los-devel-scriptsQ2. Is this ROM suitable as a daily driver?A2. It might be, depending on your requirements. You would need to try it yourself, with your preferred apps, to see if suits your purposes. I've been using it myself since mid April 2022 with no major issues.Q3. What do I do if my app xyz doesn't work?A3. I can't help diagnose problems with random apps I know nothing about. If the app is critically important to you and it doesn't work on this ROM, go back to a ROM where it did work.Q4. Why is this ROM laggy and/or buggy?A4. The device will be noticeably slower if you're using any Gapps package. Consider going gapps-free. A lot of apps will work without Google's services, or there exist alternatives that will. Check out F-Droid, Aurora Store, NewPipe, etc.Q5. What TWRP should I use?A5. I use official TWRP 3.6.1_9. Get it from
https://twrp.me/samsung/samsunggalaxytabs280ltexx2015.htmlQ6. Why should I use this ROM?A6. You don't have to! If you don't like it, go back to your old ROM.Q7. Will you offer monthly updates with security patches?A7. I plan to do so. I will try to update the ROM with the monthly security patches after LineageOS has released them, free time permitting. Each monthly build will be quickly tested to make sure the ROM still works, before it's made available (which might in some cases delay the release).Q8. I'm a newbie. Can you provide step by step instructions?A8. We simply don't have the time to do this, but there are lots of tutorials, videos, etc online showing how to flash custom ROMs and how to deal with common problems. Newbie questions are also accepted in the XDA General Questions and Answers forum. Having said that, @pflyaz has kindly make a guide in post #37.Q9. Can I report a bug with respect to the ROM?A9. Yes, but you need to supply the following information. If you don't, I won't look at it.
Provide an adb logcat of the problem, and if possible describe how to reproduce it. Note that I can't help if it involves downloading any app I don't already use that requires payment or creating a userid/password.
To get a logcat, open a terminal window on your PC, connect your device to it via USB, and do this:
Bash:
# clear the logcat first
adb logcat -c
# start logcat trace
adb logcat > problem.txt
# reproduce problem
# wait until problem has occurred,
# then stop trace by hitting ctrl-c then zip the problem.txt file
# before uploading it.
Q10. How long will you build 18.1 for this device?A10. For now, 18.1 will be built for all of 2022. After that, we will make a decision depending on a number of factors.Q11. Do I need to erase everything and format my data before installing this ROM for the first time?A11. Under most circumstances, yes.
If you're coming from stock Samsung Android, or an earlier version of LineageOS, or a different custom ROM, you MUST 'clean flash': boot to TWRP recovery, wipe system, data, dalvik/art cache, and cache partitions, then Format Data, then install this ROM.
If you don't do this you're likely to run into problems, such as getting stuck at the boot animation for more than 5 minutes.Q12. What Gapps should I use?A12. Your choice! There are several well-known Gapps packages, such as NikGapps, BiTGapps, OpenGapps, and MindTheGapps. OpenGapps is being removed as per this post. Do your own research as to what is the most reliable gapps option for you.
I recommend installing the SMALLEST version of any of these, preferably with just the minimum Google services needed to access the Play Store and run apps that depend on Google services.
You could also consider Google alternatives, such as Aurora Store, which mirrors the Google Play Store apps but doesn't need any Google services itself. Many Play Store apps do not actually depend on Google services.
If you are going to install any Gapps package, follow the installation instructions given for that particular package.Q13. I'm having problems with Gapps. Can you tell me why it's not working?A13. I can't answer any questions about Gapps, because I don't use them. Ask your questions on the XDA thread for the Gapps package you're using.Q14. Why isn't my post answered?A14. There are several possible reasons: the question is answered in the FAQ (in which case it will be ignored completely); or it involves apps or operating systems that I don't use; or it's about Gapps, which I don't use; or I simply have not had time to answer any questions.Q15. What speed up/optimization tips do you suggest?A15. These steps can make a big difference to performance:
Turn off animations. Go to Settings > System > Developer options, scroll down to the Drawing section, and set Window, Transition and Animator scale all to "Animation off".
Don't install Gapps unless you depend on something that only Google is providing. Use Aurora Store to get your preferred Play Store apps - they will all be available on Aurora Store. You can choose to access this anonymously or use a Google account.
Don't run more than two apps at the same time. You can probably listen to music in the background and use a web browser at the same time.
Use a web browser with built-in adblock and privacy features, such as Brave.
Use NewPipe to watch your streaming content. It has built in adblock so you don't have to watch forced ads.
Look for apps that are open source, ad-free and lightweight.
Q16. Does this ROM support Magisk so I can root my device?A16. Magisk works with this ROM and I'm using it, but that could change with any revision and changes by Google. However I can't help with any related issues. Direct any questions about Magisk to the XDA Magisk forum.Q17. Will this ROM ever become official?A17. Never. Official maintainers have onerous responsibilities, and I know my device trees, code organization and git commits will NOT meet LineageOS standards. I'm not able or willing to take on the responsibilities and commit the extra time to supporting an official build.Q18. What is the difference between this ROM and others?A18. This ROM tries to be pure LineageOS with little or no modification. Other ROMs may come with a different UI, different bundled apps, etc.Q19. Will there be any major 18.1 code modifications in the future?A19. I don't anticipate any major modifications. There may be some slight tweaking to the SEpolicy, small bug fixes and minor code cleanup, but all the hard work - getting the ROM up and running, and fixing all the major bugs - has been done. This doesn't mean the code is perfect or well organized, but I won't be making any major changes.Q20. Why did you fork the trees?A20. I wanted my own private branch where I could make changes that would only affect my own personal builds.Q21. Can you build a variant of this device? For example, a S-pen version?A21. I cannot and will not try to build for a variant device if I don't physically have that device. I have to be able to boot and test it myself, and there's no guarantee that I can get those variant features working. So I will NEVER build T710, T810 and T815.Q22. Does this ROM have any wifi connection issues?A22. This ROM's wifi has been stable on the specified device ever since lpedia and retiredtab determined the root cause of the wifi problems back in July 2021 and re-installed the original S2 network 'blobs' with LOS 17.1.Q23. Is this ROM secure so I can do financial transactions?A23. Although Android monthly security patches do improve general security, this ROM's outdated kernel and old proprietary vendor blobs/drivers will NEVER get updates of any kind, and could have significant security holes.
In addition, although the ROM is SElinux enforcing, there's a good chance that the rules written (about 800+ lines of code) have some errors.
If the device is rooted, this would further weaken the security.
With this information, it's up to you to make an informed decision about whether you trust this ROM to be secure enough for your financial transactions.Q24. Okay, I understand the consequences and willing to take the risks outlined, now where can I find the BETA ROM?A24. Downloads are at
https://sourceforge.net/projects/los4sgt/files/los18.1/
Please note that there are two builds for every date. Start with the enforcing build, if you hit issues, flash the permissive boot image to determine if your issue is related to SELinux. If you have Magisk installed, you first need to patch the permissive boot image with the Magisk app before flashing.
If your initial enforcing build install does not have working RIL, you might need to fix SELinux labeling of your EFS partition. To do so, use ADB in root mode. Please note that ADB root needs to be enabled in the developer options of your device. Then use the following commands from a PC connected via ADB:
Bash:
adb root
adb shell
# Check if SELinux relabeling is required, do not modify anything
restorecon -R -v -n /efs
# If you see some "Relabeling..." output, run the real relabeling
restorecon -R -v /efs
Release notes
June 18, 2023 Release
June 2023 LineageOS & Android security fixes. >5500 files changed.
May 14, 2023 Release
May 2023 LineageOS & Android security fixes. >5600 files changed
April 23, 2023 Release
April 2023 LineageOS & Android security fixes. >4600 files changed.
March 26, 2023 Release
March 2023 LineageOS & Android security fixes. >27000 files changed.
February 18, 2023 Release
February 2023 LineageOS & Android security fixes. >21000 files changed.
January 22, 2023 Release
January 2023 LineageOS & Android security fixes. >4200 files changed.
December 17, 2022 Release
December 2022 LineageOS & Android security fixes. >3800 files changed.
November 13, 2022 Release.
November 2022 LineageOS & Android security fixes. >4000 files changed.
Kernel improvements by Ananjaser
Starting with these builds I will only publish the SELinux enforcing ROM. If you encounter issues that might be SELinux-related, please first flash the boot_permissive-<date>.img as boot image and re-try to help me identify if the issue is SELinux-related.
October 22, 2022 Release.
Initial public release. First 18.1 T715 ROM with working RIL, also first 18.1 T715 ROM with SELinux in Enforcing mode. T710/T715 common code based on retiredtab's work for T710 so all his latest changes apply as well.
Reserved #3
Reserved #4
Reserved #5
Congratulations on this release @metterschling and @retiredtab , great to see!
@metterschling If you don't mind a couple of comments about your scripts, you need not have created a patch for my script. You could have just forked mine and pushed your changes to it. No need to complicate things for novice builders. Secondly, I'm sure your gts28lte tree can be a source of inspiration for the other 3 variants so as to build a complete set. Thirdly, you may be able to let gts28wifi users flash your builds if you add gts28wifi as a TARGET_DEVICE, to make it easier to cover more users in the meantime. Fourthly, you clone so many repos when it could be cleaner to fork then substitute your forks in the roomservice. This could avoid potential repo syncing errors.
ripee said:
@metterschling If you don't mind a couple of comments about your scripts, you need not have created a patch for my script. You could have just forked mine and pushed your changes to it. No need to complicate things for novice builders. Secondly, I'm sure your gts28lte tree can be a source of inspiration for the other 3 variants so as to build a complete set. Thirdly, you may be able to let gts28wifi users flash your builds if you add gts28wifi as a TARGET_DEVICE, to make it easier to cover more users in the meantime. Fourthly, you clone so many repos when it could be cleaner to fork then substitute your forks in the roomservice. This could avoid potential repo syncing errors.
Click to expand...
Click to collapse
Thank you @ripee. Just to be sure: all you above comments are related to my build environment setup script here, correct?
I agree with regards to the patch, this is how I started and just wanted to document my steps as code. During my next free cycle, I'll be looking at reworking this.
Regarding 2) as mentioned in the opening post my work is already the result of synergies between code trees for the other devices, mainly based on retiredtab's trees, and we keep the common set wherever possible.
So there is no need for 3) as gts28wifi users can directly use the equivalent one linked on the top of post #1.
For 4) I'm open for suggestions which clones you are referring to. As an example, I don't want to fork the entire LineageOS tree just to apply the small NetworkStack patch.
metterschling said:
Thank you @ripee. Just to be sure: all you above comments are related to my build environment setup script here, correct?
I agree with regards to the patch, this is how I started and just wanted to document my steps as code. During my next free cycle, I'll be looking at reworking this.
Regarding 2) as mentioned in the opening post my work is already the result of synergies between code trees for the other devices, mainly based on retiredtab's trees, and we keep the common set wherever possible.
So there is no need for 3) as gts28wifi users can directly use the equivalent one linked on the top of post #1.
For 4) I'm open for suggestions which clones you are referring to. As an example, I don't want to fork the entire LineageOS tree just to apply the small NetworkStack patch.
Click to expand...
Click to collapse
@ripee I've pushed a new version of the build environment setup script, following your guidance. Please let me know if there are more areas of improvement, very much appreciated!
November build lineage-18.1-20221113-UNOFFICIAL-gts28ltexx.zip uploaded. Please see FAQ #24 for the download link.
November 13, 2022 release notes:
November 2022 LineageOS & Android security fixes. >4000 files changed.
Kernel improvements by Ananjaser
Starting with these builds I will only publish the SELinux enforcing ROM. If you encounter issues that might be SELinux-related, please first flash the boot_permissive-<date>.img as boot image and re-try to help me identify if the issue is SELinux-related.
Enjoy!
metterschling said:
Thank you @ripee. Just to be sure: all you above comments are related to my build environment setup script here, correct?
I agree with regards to the patch, this is how I started and just wanted to document my steps as code. During my next free cycle, I'll be looking at reworking this.
Regarding 2) as mentioned in the opening post my work is already the result of synergies between code trees for the other devices, mainly based on retiredtab's trees, and we keep the common set wherever possible.
So there is no need for 3) as gts28wifi users can directly use the equivalent one linked on the top of post #1.
For 4) I'm open for suggestions which clones you are referring to. As an example, I don't want to fork the entire LineageOS tree just to apply the small NetworkStack patch.
Click to expand...
Click to collapse
If gts28wifi users get an error that their device is not gts28ltexx, then yes it would be necessary to add it as a target device in the tree. Lineage uses the networkstack repo from google, which you can tell cuz they track the aosp remote, so in this case we have nothing to fork and substitute. Only a patch of google's own repo would be convenient.
Just to clarify, since there has been discussion about the WiFi version (t713), can this ROM be safely flashed on one?
Also I believe I have a t715Y... Would this t715 ROM work on it?
(I have three Tab S2 units -- two t713 models and a t715Y.)
Thanks
KeepingItCuttingEdge said:
Just to clarify, since there has been discussion about the WiFi version (t713), can this ROM be safely flashed on one?
Also I believe I have a t715Y... Would this t715 ROM work on it?
Click to expand...
Click to collapse
The T713 and T715 have completely different chipsets. T713 is msm8976 and T715 is exynos5433.
If your T715Y is known as "gts28ltexx" OR "gts28lte" as described in post #1, then you can flash this rom on it. You can download an utility called devcheck by flar2 to verify. Your device name will be shown in the system tab under device.
https://play.google.com/store/apps/details?id=flar2.devcheck
metterschling's code checks for gts28lte,gts28ltexx using this below
https://github.com/metterschlg/andr...s28ltexx/blob/lineage-18.1/BoardConfig.mk#L17
KeepingItCuttingEdge said:
Also I believe I have a t715Y... Would this t715 ROM work on it?
Click to expand...
Click to collapse
Most likely, ROMs for the T715 work on the T715Y according to some XDA posts. Like this one. I don't own a T715Y, so can't test myself.
December build lineage-18.1-20221217-UNOFFICIAL-gts28ltexx.zip uploaded. Please see FAQ #24 for the download link.
December 17, 2022 release notes:
December 2022 LineageOS & Android security fixes. >3800 files changed.
If you are coming from a previous version of these builds, you can dirty flash, otherwise please perform a factory reset and format data before installing this ROM.
Enjoy
Hi friends, after loading from TWRP twrp-3.7.0_9-0-gts28ltexx.img.tar on my SM T710, my tab gets stuck on booting with lineageos graphics. I made the backup with TWRP if I upload the files can I repair the tab as before?
mikelosat said:
Hi friends, after loading from TWRP twrp-3.7.0_9-0-gts28ltexx.img.tar on my SM T710, my tab gets stuck on booting with lineageos graphics. I made the backup with TWRP if I upload the files can I repair the tab as before?
Click to expand...
Click to collapse
If I understand correctly, you picked the gts28ltexx version which is for the SM-T715. If your device is the SM-T710 (gts28wifi) I'd strongly recommend to use the ROM and matching TWRP linked in this thread.
If your device is SM-T715, please see FAQ #5 in post #2 of this thread. I use the downlevel TWRP because newer ones did not work for me.
I use a SAMSUNG SM-T715 device just as described:
Model: SM-T715 (LTE) - gts28ltexx - 8" screen, Exynos 5433 SoC, LTE.
To be able to install the ROM I used "TWRP twrp-3.7.0_9-0-gts28ltexx.img.tar"
After several attempts I could neither restore the BACKUP nor start the operating system. I had to do a complete WIPE and at that point lineageos advanced, now I'm having problems, I don't have the gapps I downloaded version 11 for ARM but despite having enough space it gives me an error "70" not enough space. I have no google services and no PLAYSTORE, I am in a critical situation, how can I install the google PlayStore? I can't even add gmail account from settings, it's a disaster.
metterschling said:
If I understand correctly, you picked the gts28ltexx version which is for the SM-T715. If your device is the SM-T710 (gts28wifi) I'd strongly recommend to use the ROM and matching TWRP linked in this thread.
If your device is SM-T715, please see FAQ #5 in post #2 of this thread. I use the downlevel TWRP because newer ones did not work for me.
Click to expand...
Click to collapse
Finally I come to the conclusion, after fully formatting my SAMSUNG SM T715 the ROM started up, the problem was the wrong recovery, using the version indicated in the guide above everything started up correctly.
Unfortunately this ROM is full of bugs and its use is useless, below I will list all the problems it causes during use:
1. 4g calls don't work, during the call you can't hear anything either incoming or outgoing.
2. Bluetooth only works with music while in call it remains mute.
3. the only way to call is to keep the speakerphone open otherwise the call will be silent.
4. Whatsapp is impossible to use and only allows you to use it in beta.
5. Smart Switch as for whatsapp does not work with custom ROMs
6. Does not sync contacts even though sync has started.
It's really a shame after all these hours to find that you've only wasted so much time.
Maybe I've done something wrong, I don't rule it out, maybe someone will be able to give me some advice.