[ROM][International][4.2.2] 2013-07-16 Paranoid Android 3.67 - now with HALO! - HTC One X+

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Here's my first ever ROM release
This is completely stock Paranoid Android, with modifications to certain packages to fix things like camera, mobile data and audio. I'll update the second post with my local_manifest containing all repos used that aren't part of the official PA manifest.
I've included corne's PerformanceTool and ShareLogs app as well as the CM10.1 LockClock and Torch as i used them a lot and so wanted them here too
Known Issues...
The boot.img included will boot but for now is not recommended as wifi and mobile data won't work so please flash the latest BLADE 42 kernel (current latest is boot-BLADE-42-201305041517.img)
While i'm happy to share these builds, I don't really have the time to support them so I'll help where I can but hopefully the community will help each other out and no issue will be looked in to without the logs from ShareLogs. Also, feel free to make pull requests to any of my repos if you have any fixes that you'd like included
Downloads
BLADE kernel
ROM (MD5: 7d50007da2817a2b8357d346f3a0259d)
CM GAPPS (if you use the PA GAPPS you'll need to push Gallery2.apk from the ROM as the one bundled with their gapps will force close on face detection)
Installation
Install kernel from bootloader
Code:
fastboot flash boot boot-BLADE-42-201305041517.img
A factory reset and system wipe is always recommended (use Titanium to backup/restore your apps and data) but may not be required. If you have issues, please try and recreate them after a factory reset/system wipe before reporting them.
Install ROM and GAPPS from recovery
Wipe cache/dalvik
Reboot.
Note: Once the setup wizard is finished, you may need to press home for the launcher to show.
Thanks to...
ParanoidAndroid Team
CyanogenMod Team
Maxwen and Lloir for the device tree
Maxwen again for his kernels
corne for his PerformanceTool and ShareLogs tool

Changelog
2013-07-11:
Added hardware keys to framework overlay to enable the remapping settings option
Merged all forked repos with PA
2013-06-26:
Added Stk fix (thanks maxwen)
Merged all forked repos with PA
2013-06-11:
Rebased the device tree on this
Repo synced all projects and merged in any changes to repos that i've forked
2013-05-20:
Repo synced all projects and merged in any changes to repos that i've forked
Synced device tree with maxwens
Added 'Advanced Settings' option to Settings that calls EndeavoruParts for kernel related options (s2w, backlight notifications, etc)
2013-05-06 [link]
First release
Known Issues
MHL

Building the ROM yourself
If you want to contribute to the ROM, you'll first need to be able to build it. Here's how.
First, follow the guide here up to the repo init line to get your build environment set up.
Next, create a folder for ParanoidAndroid. For the purposes of this guide, i'll assume it's in ~/Android/PA
Initialise the repo
Code:
cd ~/Android/PA
repo init -u git://github.com/ParanoidAndroid/manifest.git -b jellybean
Download https://raw.github.com/tombriden/device_htc_enrc2b/pa/roomservice.xml and put it here, ~/Android/PA/.repo/local_manifests/
so that you have all the repos with mods/fixes for the one x+
Now, sync the repo. This step may take a while.
Code:
repo sync -j6
Edit the following PA vendor file, ~/Android/PA/vendor/pa/products/AndroidProducts.mk , and append the following to the bottom
Code:
ifeq (pa_enrc2b,$(TARGET_PRODUCT))
PRODUCT_MAKEFILES += $(LOCAL_DIR)/pa_enrc2b.mk
endif
Create the following file and paste this into it; ~/Android/PA/vendor/pa/products/pa_enrc2b.mk
Code:
# Check for target product
ifeq (pa_enrc2b,$(TARGET_PRODUCT))
# OVERLAY_TARGET adds overlay asset source
OVERLAY_TARGET := pa_xhdpi
# include ParanoidAndroid common configuration
include vendor/pa/config/pa_common.mk
# Inherit CM device configuration
$(call inherit-product, device/htc/enrc2b/cm.mk)
PRODUCT_NAME := pa_enrc2b
#GET_VENDOR_PROPS := $(shell vendor/pa/tools/getvendorprops.py $(PRODUCT_NAME))
endif
And finally, build the rom
Code:
~/Android/PA/rom-build.sh enrc2b

Is it the version with halo in it, or is that not yet released in the source code?

Looks good, I'll probably flash this later. Do you think you could put a bug list in the first post so I'll be aware of what's not working. It's 4.2.2, something has to not work properly.

Ranomez said:
Is it the version with halo in it, or is that not yet released in the source code?
Click to expand...
Click to collapse
No halo, doesn't seem to be in the repos yet.

sandsrules said:
Looks good, I'll probably flash this later. Do you think you could put a bug list in the first post so I'll be aware of what's not working. It's 4.2.2, something has to not work properly.
Click to expand...
Click to collapse
The only thing would be MHL (although i've not tried it) as the device tree is pretty much the same as maxwen's AOKP ROM so if it doesn't work on that ROM it won't here
I've tested
calls
mobile data
wifi
bluetooth
bluetooth tether
camera front and back
gps

Lol I've just installed a new ROM this morning and here's a new one already? looks good
Sent from my HTC One X+ using xda app-developers app

HI !
Trying it first time and have an issue at the stage -
repo sync -j6
The error message is -
[email protected]:~/Android/PA$ repo sync -j6
fatal: duplicate project CyanogenMod/android_packages_apps_Torch in /home/baudy/Android/PA/.repo/manifest.xml
What could be the issue ?
Thanx !

baudy2 said:
HI !
Trying it first time and have an issue at the stage -
repo sync -j6
The error message is -
[email protected]:~/Android/PA$ repo sync -j6
fatal: duplicate project CyanogenMod/android_packages_apps_Torch in /home/baudy/Android/PA/.repo/manifest.xml
What could be the issue ?
Thanx !
Click to expand...
Click to collapse
My guess is you ran the repo init command from the howto for CyanogenMod and then the one here for PA as well? Delete the PA folder, create again and just do the repo init for PA
Code:
repo init -u git://github.com/ParanoidAndroid/android.git -b jellybean

everything working greate. 10x

wackymix said:
everything working greate. 10x
Click to expand...
Click to collapse
how about battery?

freemod said:
how about battery?
Click to expand...
Click to collapse
flash it and find out

freemod said:
how about battery?
Click to expand...
Click to collapse
battery usage is only minimal dependent on the rom
it's always people that will screw it up
Sent from my HTC One X+ using xda app-developers app

Everything works fine here. Quick question though, how do I enable the halo feature? I have PA 3.5 on my Nexus 7 and the halo icon is on the status bar but that doesn't seem to be the case on my HOX+. Am I missing something?

monstereo said:
Everything works fine here. Quick question though, how do I enable the halo feature? I have PA 3.5 on my Nexus 7 and the halo icon is on the status bar but that doesn't seem to be the case on my HOX+. Am I missing something?
Click to expand...
Click to collapse
Halo is only available on Nexus devices at the minute. Once the source has been pushed to the repos, it'll be in the rom

tbriden said:
Halo is only available on Nexus devices at the minute. Once the source has been pushed to the repos, it'll be in the rom
Click to expand...
Click to collapse
I see, Thanks for that quick reply :good:

tbriden said:
My guess is you ran the repo init command from the howto for CyanogenMod and then the one here for PA as well? Delete the PA folder, create again and just do the repo init for PA
Code:
repo init -u git://github.com/ParanoidAndroid/android.git -b jellybean
Click to expand...
Click to collapse
Did not help... The same error message. Other advices ?
If i do not create the file ~/Android/PA/.repo/local_manifests/roomservice.xml the repo sync starts fine...
Why it is so ?

Well there shouldn't be any CyanogenMod repos in the PA manifest, which is why it's in the local_manifest or there'd be no torch. You can remove just that line from the local manifest, you'll need the rest of it for the buld to work at all on the hox+.
Can you copy the content of ~/Android/PA/.repo/manifest.xml to pastie.org and link it here
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD

tbriden said:
Well there shouldn't be any CyanogenMod repos in the PA manifest, which is why it's in the local_manifest or there'd be no torch. You can remove just that line from the local manifest, you'll need the rest of it for the buld to work at all on the hox+.
Can you copy the content of ~/Android/PA/.repo/manifest.xml to pastie.org and link it here
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
This is my ~/Android/PA/.repo/manifest.xml - http://pastie.org/7816737
I removed the Torch line and some others from roomservice.xml (as i had the same error for other lines). Mostly they were "remove ....."
Now my roomservice.xml looks like this and is working -
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="packages/apps/LockClock" name="CyanogenMod/android_packages_apps_LockClock" remote="github" revision="cm-10.1" />
<project path="packages/apps/Torch" name="CyanogenMod/android_packages_apps_Torch" remote="github" revision="cm-10.1" />
<project name="cornedor/performance-tool" path="packages/apps/PerformanceTool" remote="github" revision="master" />
<project name="cornedor/share-logs" path="packages/apps/ShareLogs" remote="github" revision="master" />
<project name="tombriden/device_htc_enrc2b" path="device/htc/enrc2b" remote="github" revision="pa" />
<project name="maxwen/enrc2b-kernel-BLADE" path="kernel/htc/enrc2b" remote="github" revision="master" />
<project name="maxwen/bluedroid" path="external/bluetooth/bluedroid" remote="github" revision="jb-mr1" />
<project name="tombriden/android_frameworks_av" path="frameworks/av" remote="github" revision="jb-mr1.1-release" />
<project name="tombriden/pa_android_frameworks_base" path="frameworks/base" remote="github" revision="jellybean" />
<project name="tombriden/pa_android_frameworks_opt_telephony" path="frameworks/opt/telephony" remote="github" revision="jellybean" />
<project name="tombriden/pa_android_frameworks_native" path="frameworks/native" remote="github" revision="jellybean" />
<project name="tombriden/pa_android_system_core" path="system/core" remote="github" revision="jellybean" />
<project name="tombriden/android_hardware_libhardware" path="hardware/libhardware" remote="github" revision="jb-mr1.1-release" />
<project name="tombriden/android_hardware_libhardware_legacy" path="hardware/libhardware_legacy" remote="github" revision="jb-mr1.1-re$
<project name="tombriden/android_packages_apps_Camera" path="packages/apps/Camera" remote="github" revision="jb-mr1.1-release" />
</manifest>

Related

[Pre Alpha][Unofficial][CM-11.0][4.4.4][SM-G7102][Galaxy Grand 2]NOT A DAILY DRIVER

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WARNING! This ROM is for the SM-G7102 variant only!
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KitKat), which is designed to increase performance and reliability over stock Android for your device.
Code:
/* * 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. You can also view the Changelog for a full list of changes & features.
Device-specific source code for the Samsung Galaxy Grand 2 Duos are available from
Device :- https://github.com/k2wl/android_kernel_samsung_ms013g
Kernel :- https://github.com/k2wl/android_device_samsung_ms013g
Vendor :- https://github.com/k2wl/android_vendor_samsung_ms013g
I am doing this in my free time. So forcing me for updates and bug fixes and feature request will be ignored.
Please don’t ask for ETAs for bugs, your questions about ETAs will be ignored.
Asking for ETAs is against XDA rules.
Although i will work on bugs still cant say when they will be fixed.
please be nice in your words. we all are family. don’t abuse the fellow members.
Follow the rules
read the thread before asking questions.
you are free to post bugs here .
Click to expand...
Click to collapse
Screenshots:-
Downloads
pre alpha build 1
http://d-h.st/NPB
Working :-
1.Missed calls
2.SMS
3.WIFI
4.Bluetooth
5.Sound
6.Data
7.vibration
Not Working:-
1.Outgoing calls,Incoming calls
outgoing call works but it is muted...bilaterally
incoming call can't be picked up but can send a sms that i m busy.
incoming call hang up works partially as it stays on hanging up screen.
2.Camera
3.bootloop while added libsecnativefeature.so
Installation:-
1.Install CWM /PHILZ 4.4
you can use following cwm 6.0.5.1 latest source build
http://d-h.st/XDF
2.copy rom and libsecnativefeature.so to sd card
3.boot in recovery
4.wipe cache/data/davlik cache
5.install from sdcard
6. after boot it will bootloop on cm logo
attach phone to the pc
give following commands
adb remount && adb shell rm system/lib/libsecnativefeature.so && adb shell reboot
Click to expand...
Click to collapse
7.after phone is booted....keep it aside for 5 min before using it again
8.now copy libsecnativefeature.so from your sdcard to system/lib folder using cm file manager
9.this should give you prompt for new sim cards
How to contribute:-
1.post bug fixes here
2.compile rom yourself..make changes to source to fix bugs...send me a pull request on github
3. suggest fixes by searching on google or xda or asking your developer friends.
How to compile cm-11.0 from source
1.download the source form cyanogenmod repo
2.add following local manifest as ms013g.xml in .repo/local_manifests
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_hardware_qcom_display-caf-new" path="hardware/qcom/display-caf-new" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_hardware_qcom_media-caf-new" path="hardware/qcom/media-caf-new" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_hardware_qcom_fm" path="hardware/qcom/fm" remote="github" revision="cm-11.0" />
<project name="k2wl/android_device_samsung_ms013g" path="device/samsung/ms013g" revision="cm-11.0" remote="github" />
<project name="k2wl/android_kernel_samsung_ms013g" path="kernel/samsung/ms013g" remote="github" revision="cm-11.0" />
<project name="k2wl/android_vendor_samsung_ms013g" path="vendor/samsung/ms013g" remote="github" revision="cm-11.0" />
</manifest>
Code:
mkdir cm11
cd cm11
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
nano .repo/local_manifests/ms013g.xml
(copy contents from above xml code to this file and then cltr+o , enter and cltr+x)
Code:
repo sync
cd ~/cm11/vendor/cm
./get-prebuilts
cd ~/cm11
. build/envsetup.sh
brunch ms013g
Sources:-
Just a statement regarding sources: The source is released for all at GITHUB repo given above. BUT Free software does NOT mean no work or time was spent working on it. A lot of my free time has gone into patching/testing this rom. If you use my modified source in parts or in its entirety, I kindly ask you mention its origins and to send me a github pull request or PM whenever you find bugs or think you can help improve my rom further. This way the entire community will truly benefit from the spirit of open source.
Thank you !
Credits:-
1.cyanogenmod team
2 @dhacker29 for his contribution to falcon and cm source code for dual sim
most of the device tree based on work of @dhacker29 on falcon
3.samsung for kernel sources (@rutvik95 for providing kernel sources on github)
4.CAF for some kernel patches
5 @Rox my friend from s3 neo forum for providing me guidence for various bug fixes.
6 @Quarx from LG L90 forum for his awesome work on LG l90
7. may be some more
remind me if i forgot someone
reserved
reserved 2
Ohh my god ! It's good news for Grand 2 Family.
Very excited now ! It's really unbelievable.
Thanks @k2wl & whole CM team.
Bro @k2wl, eagerly waiting for ur Complete CM11 for G2............
Hopefully, very soon we will be going to Download the Complete CM11 ROM for our G2..........
Sent from my SM-G7102 using Tapatalk
i need boot.img from G7102DDUBNJ2 firmware...
any one having that firmware????
k2wl said:
i need boot.img from G7102DDUBNJ2 firmware...
any one having that firmware????
Click to expand...
Click to collapse
https://www.dropbox.com/s/qqzyis3uomlpj8a/boot.img?dl=0
If i take a nandroid backup before installing this rom then restore it. Will i have any problems? @k2wl ?
Sent using XDA Premium app.
Calls not working ?
Muted
keshavt said:
If i take a nandroid backup before installing this rom then restore it. Will i have any problems? @k2wl ?
Sent using XDA Premium app.
Click to expand...
Click to collapse
if you install nandroid back up after installing this you will get back to your stock rom you are using.
@ nar67 read first post ...
k2wl said:
if you install nandroid back up after installing this you will get back to your stock rom you are using.
@ nar67 read first post ...
Click to expand...
Click to collapse
hey bro good news for us android Lollipop AOSP source available.
Please update us about the progress?
Sent using XDA Premium app.
keshavt said:
Please update us about the progress?
Sent using XDA Premium app.
Click to expand...
Click to collapse
still stuck with camera hal...until camera hal is resolved we cant move on to next thing....
@manan001 android l is very much big step......even cm team will have hard time supporting their all devices...right now....too many changes ...to code...security...requirements...i dont think we should worry of android l right now....may be after january 2015 when cm code stables we can look into it.
Some bugs that i would like to inform you.
Credits: David Parker
Sent using XDA Premium app.
Progress update please?
Sent using XDA Premium app.
keshavt said:
Progress update please?
Sent using XDA Premium app.
Click to expand...
Click to collapse
Check This Quote From OP ...Developer will update anything whenever its necessary hence no need of asking the same has it will look like asking ETA itself ...Developer has other works too so just wait if nay updates/progress is needed to be updated then k2wl will update
Quote:
I am doing this in my free time. So forcing me for updates and bug fixes and feature request will be ignored.
Please don’t ask for ETAs for bugs, your questions about ETAs will be ignored.
Asking for ETAs is against XDA rules.
Although i will work on bugs still cant say when they will be fixed.
please be nice in your words. we all are family. don’t abuse the fellow members.
Follow the rules
read the thread before asking questions.
you are free to post bugs here .
Click to expand...
Click to collapse
Any new for this rom ?
@k2wl did the gps works very good? If yes. Pls try sending me the gps binary from cm . cause i wanna try. .. Maybe bad gps is at stock driver/binary thx
If you like my post.. Dont say thanks... Click the Thanks Button
CM 12 now working with grand i9082
CM 11 not working with my grand sm-7102 ???
My grand 2 is hard bricked. so i have no device anymore. but i will keep building for grand 2.
thanks.

[17.04][ROM][5.1] CyanogenMOD 12.1 [UNOFFICIAL]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​Ok, less words, more CM
Remember, this is unofficial and there is no guarantee for this!
I am only a builder, so 99% of bugfixing is on CM team.
Builds are produced Every Other Day
Latest build 17.04: http://forum.xda-developers.com/showpost.php?p=60169657&postcount=1075
Source:
CyanogenMOD https://github.com/CyanogenMod
OnePlus One kernel https://github.com/CyanogenMod/android_kernel_oneplus_msm8974/tree/cm-12.1
Credits:
CM Team
smoki3 for a lot of help
Installation:
FC with setup fixed, so nothing special, like any rom!
Bugs:
wow so much bugs here. Or not?
When open "Select and order tiles" Settings FC. Temp fix - use custom theme
When installing apk with file manager, Package installer crashes, but App will be installed. No problems with market / Titanium Backup
When recieve SMS, SMS app FC. Temp fix - use another message app (Google Chat, Hangouts)
Alarm FC
Contacts FC
Navbar glitch
Contacts import FC
More?
CM Gerrit
(merged: branch 12.1) http://review.cyanogenmod.org/#/q/status:merged+branch:cm12.1,n,z - you can see recent changes here
(open: branch12.1) http://review.cyanogenmod.org/#/q/status:open+branch:cm-12.1,n,z - helpful for devs, may contain build fixes
Changelog:
Code:
03.24
initial release
03.24 V2
Sync CM code
Fixed navbar
Disabled block-build mode (just /system folder)
03.25
Sync CM code
Fixed Alarm FC
Fixed QS adding FC
Fixed App installer FC
Fixed SMS FC
Remove CM Setup, you can flash as always, no FC
03.27
Sync CM code
Many fixes and improvements by CM (check CM gerrit)
Switch to almost pure CM sources (only PackageInstaller from Euphoria, we need it)
Android 5.1.0 R3
Bring back CM setup (FC fixed)
Remove CM updater (its useless here)
03.28
Sync CM code (see gerrit for more details)
Another painful attempt to fix SMS. Hope this time it will work
Cherry-picked commit to fix Contacts FC
03.29
Sync CM code
Update msm8974-common blobs. Device specific proprietaries at next.
Little remake of bootanimation, to be more individual
03.31
Sync CM code
Fixed BT audio
100% pure CM source
Final fix for SMS app
Revert bootanim. It's now in Addons post.
Updated build instuction
04.04
Sync CM code
04.06
Sync CM code
04.08
Sync CM code
Remove damn firmware check. Now no "error executing blablabla" for everyone. Use any modem what you like
04.10
Sync CM code
04.12
Sync CM code
Fix alarm wakelock
04.14
Sync CM code
Android 5.1.0 R5
04.17
Sync CM code
Wi Fi fixes
Merged translations
Some videos (Benchmark, Installation, Review) by @savadam
Download:
ROM
GAPPS
GAPPS Minimal - my choise
ADDONS
About phone screenshot
Quick build instruction:
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-12.1
repo sync
Code:
mkdir .repo/local_manifests
nano .repo/local_manifests/local_manifests.xml
Paste this:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_oneplus_bacon" path="device/oneplus/bacon" remote="github" revision="cm-12.1" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-12.1" />
<project name="CyanogenMod/android_device_oppo_msm8974-common" path="device/oppo/msm8974-common" remote="github" revision="cm-12.1" />
<project name="CyanogenMod/android_device_oppo_common" path="device/oppo/common" remote="github" revision="cm-12.1" />
<project name="CyanogenMod/android_kernel_oneplus_msm8974" path="kernel/oneplus/msm8974" remote="github" revision="cm-12.1" />
<project name="TheMuppets/proprietary_vendor_oppo" path="vendor/oppo" remote="github" revision="cm-12.1" />
<project name="TheMuppets/proprietary_vendor_oneplus" path="vendor/oneplus" remote="github" revision="cm-12.1" />
</manifest>
Code:
repo sync
Build it:
Code:
. build/envsetup.sh && breakfast bacon && brunch bacon
To build new version, do:
Code:
make clean
repo sync
And every step from "Build it" section
If you got error with incorrect java, do:
Code:
export JAVA_HOME=/usr/lib/jvm/java-7-openjdk-amd64/ && export PATH=$JAVA_HOME/bin:$JAVA_HOME/jre/bin:$PATH && export CLASSPATH=$CLASSPATH:$JAVA_HOME/lib:$JAVA_HOME/jre/lib && java -version
Very nice guilde for CM roms here, I was guided by it
First!
you did it, at last!
nice rom thx
Blimey!:laugh:
Gaaps ?
Is official cm 12.1 out?
-Fabione- said:
Is official cm 12.1 out?
Click to expand...
Click to collapse
no
saiwala said:
Yes! :good:
Click to expand...
Click to collapse
No no no! Its unofficial!
mdda7 said:
Gaaps ?
Click to expand...
Click to collapse
Try the Banks Gapps. They are updated to 5.1.
http://fitsnugly.euroskank.com/?rom=banks&device=gapps
Anyone tested this? Is everything working? Are there all features from normal CM12 included (DT2W, Buttons, etc)?Thanks
All working here except for quick tile configuration fc
I can't get past the setup wizard. keeps crashing.
I've used the 5.1 gapps linked in the OP.
minty1978 said:
I can't get past the setup wizard. keeps crashing.
I've used the 5.1 gapps linked in the OP.
Click to expand...
Click to collapse
sorry, i dont tested with this gapps. I only found them on forum
no problem, I will try the banks ones..
Yup, the banks gapps work fine:
http://fitsnugly.euroskank.com/?rom=banks&device=gapps
acuicultor said:
All working here except for quick tile configuration fc
Click to expand...
Click to collapse
Good to know, thanks. What features are already implemented?
Falster said:
Good to know, thanks. What features are already implemented?
Click to expand...
Click to collapse
everything from CM12
Very nice build. The only issue I found was if I used bank gapps in OP it would force close on set up wizard. I could only continue on to the rom if I didn't use gapps at all. This may just be on my phone. Very nice start though and Glad to see this Finally. Thank you so much.
"Chance Favors the Prepared"
New build up!
-Sync CM code
-Fixed navbar
-Disabled block-build mode (just /system folder)
Added installation guide to OP
https://drive.google.com/file/d/0B4aqk_6IcgySNFZOUnlxdlhsaDA/view?usp=sharing

[ROM][9.0] LineageOS 16.0

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 9.0 (Pie), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* 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.
*
*/
LineageOS 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). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for Lineage OS is available in the LineageOS Github repo. And if you would like to contribute to Lineage OS, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions
First time flashing Lineage OS 16.0 your device?
Coming from a SENSE ROM?
Enable all location services: Settings > Location > (all location services) = On
Coming from another ROM?
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe data & cache partitions of your device (required when coming from stock!).
Flash LineageOS.
Optional: Install the Google Apps addon package.
Downloads
Downloads
ROM - https://mirror.codebucket.de/claymore1297
Google Apps - http://opengapps.org/?arch=arm64&api=9.0&variant=nano
TWRP Recovery - https://github.com/CaptainThrowback/android_device_htc_hima/releases
XDA: DevDB Information
LineageOS 16.0, ROM for the HTC One (M9)
Contributors:
@Claymore1297
@k4y0z
ROM OS Version: 9 Pie
ROM Kernel: Linux 3.10.108
Kernel Source: https://github.com/Claymore1297/android_kernel_htc_msm8994
SELinux: enforce
Requirements
HTC Firmware: 4.x
TWRP: 3.3.0-0
special thanks to:
@root-expert
Version Information
Status: Beta
What is working
WiFi
Bluetooth
IR
Camera (including video recording)
Telephony (Calls, MMS/SMS and Mobile data)
Audio (Record and Playback)
Video Playback
GPS
NFC
What is not working
FM Radio
Bug report
Bug reports without a proper description of the issue and a log will be ignored!
You don't know howto take a log - see here:
https://www.xda-developers.com/how-to-take-logs-in-android/
https://lmgtfy.com/?q=how to get android logs&p=1&s=g
How to Build
To setup the build environment, follow instructions here: https://wiki.lineageos.org/devices/himaul/build
Remember to change cm-14.1 to lineage-16.0
Create the direct and file .repo/local_manifests/roomservice.xml and add the following:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="Claymore1297/android_device_htc_himawl" path="device/htc/himawl" remote="github" />
<project name="Claymore1297/android_device_htc_himaul" path="device/htc/himaul" remote="github" />
<project name="Claymore1297/android_device_htc_hima-common" path="device/htc/hima-common" remote="github" />
<project name="Claymore1297/android_kernel_htc_msm8994" path="kernel/htc/msm8994" remote="github" />
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" />
<project name="Claymore1297/proprietary_vendor_htc" path="vendor/htc" remote="github" />
<project name="LineageOS/android_packages_apps_FlipFlap" path="packages/apps/FlipFlap" remote="github" />
<remove-project name="LineageOS/android_hardware_qcom_audio" />
<project name="Claymore1297/android_hardware_qcom_audio" path="hardware/qcom/audio-caf/msm8994" revision="p9.0-caf-8994" remote="github" />
<project name="Claymore1297/JamesDSPManager" path="packages/apps/JamesDSPManager" remote="github" />
<project name="AICP/frameworks_opt_jamesdsp" path="frameworks/opt/jamesdsp" remote="github" revision="p9.0" />
</manifest>
Things for successful builds:
Code:
cd <build LOS-root-dir>
. build/envsetup.sh
repopick -t pie-aosp-wfd
brunch himaul (for himaul)
brunch himawl (for himawl)
Screenshots
First!
Changelog
2018-12-10:
december ASB's
ambient display
Wifi direct fixed
2018-11-14:
november ASB's
whatsapp + instagram video playback issue fixed
2018-10-14:
Wifi Hotspot: fixed
Wifi disconnects when device sleeps: fixed
saving pics/vids on external sdcard: fixed
3rd party cam-apps working now (like Footej camera)
NFC fixes (namely Mifare-support, Android Beam)
2018-10-12:
october ABS's
latest N camera libs
re-add Snap camera-app
SELinux enforce
2018-10-05:
NFC
Whatsapp video playback
M4A audio playback
2018-09-29:
WiFi
Bluetooth
IR
Camera (including video recording)
Telephony (Calls, MMS/SMS and Mobile data)
Audio (Record and Playback)
Video Playback
GPS
can not load you?
Gửi từ SM-G930F của tôi bằng cách sử dụng Tapatalk
Repo gone private ?
Access Denied
Looks like you don't have permission to access this folder. Make sure you are signed in to an account that has permission, or check with the developer to request access. Only the developer/uploader can provide you with access to their restricted files.
Click to expand...
Click to collapse
GamaPL said:
Repo gone private ?
Click to expand...
Click to collapse
My bad! Link in OP correct now!
Can you provide some screenshot of the rom please?
xhoi287 said:
Can you provide some screenshot of the rom please?
Click to expand...
Click to collapse
see second post
Claymore1297 said:
see second post
Click to expand...
Click to collapse
Oh okay thanks
Is it advisable to flash this now or wait for a much stable build?
Thevenine said:
Is it advisable to flash this now or wait for a much stable build?
Click to expand...
Click to collapse
that up to you, but if no one test this, we can't figure out what's left
In my opinion it's stable. Got no random reboots or something like this.
Claymore1297 said:
that up to you, but if no one test this, we can't figure out what's left
In my opinion it's stable. Got no random reboots or something like this.
Click to expand...
Click to collapse
Is it advisable to restore a titanium backup of aicp 8.1.0 on this rom?
The Washington server its too slow for me
Downloading now, I can't wait to test this and use it as a daily driver if it is ok..
But Clay, one thing I'm fearing is the battery, is the battery okay based on ur 3 days of usage?
Thank you so much!!
tigerland said:
Downloading now, I can't wait to test this and use it as a daily driver if it is ok..
But Clay, one thing I'm fearing is the battery, is they battery is okay based on ur 3 days of usage?
Thank you so much!!
Click to expand...
Click to collapse
well, that's maybe too early to say. But my first impression was, that on screen-off the battery is much better than on O...
If possible, could you please upload the ROM also somewhere else than AFH with their potato servers? Download speed at ~20 KB/s is horrible.
Pawbrotm said:
If possible, could you please upload the ROM also somewhere else than AFH with their potato servers? Download speed at ~20 KB/s is horrible.
Click to expand...
Click to collapse
i have same problem too
Pawbrotm said:
If possible, could you please upload the ROM also somewhere else than AFH with their potato servers? Download speed at ~20 KB/s is horrible.
Click to expand...
Click to collapse
Same problem here as well
Claymore1297 said:
see second post
Click to expand...
Click to collapse
sim not supported why?

[Unofficial] AICP 14 - Galaxy Note 4 (Snapdragon) [TRLTE][TBLTE][TRLTEDuos]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!!
Until Android Lollipop, the ROM has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM.
With the re-brand of CM to LineageOS (LOS) we became LineageOS based with some tweaks from AOSP and we are now based on the "Ground Zero Open Source Project" (GZOSP) for Android Pie.
If there are any bugs, either we will sort them out or the GZOSP team, if it concerns their code base. This ROM isn't GZOSP supported, so there is no need to report errors/bugs to them!!
Code:
#include <std_disclaimer.h>
/*
* 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. Hard & a lot.
*
*/
Feature list (rough overview)
In the beginning we would like to thank:
GZOSP team
LineageOS & CM (R.I.P.) team
@maxwen and the rest of the OmniRom team
DU team
SlimRoms team
Resurrection Remix team
Community
...
Specifically for the TRLTE Build-
@Inkypen
@LorD ClockaN
@zipsnet
@eyosen
@semdoc
@SpiritCroc
@wartomato
@eboye
plus the rest of the crazy bunch that we call "team"
...
We are paying for servers that build nightlies/weeklies and everything that comes with it, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
TWRP for Samsung Galaxy Note 4 (Qualcomm)
Latest Release AICP Version 14.0
Download links:
- SM-N910F/G/P/R4/T/T3/V/W8: trlte
- SM-N9100ZC/ZH/6W/9W: trlteduos
- SM-N915F/G/P/R4/T/W8: tblte
Google Apps:
Open GApps
Select ARM and 9.0. Variant is of your own choosing. Suggested: Pico or Nano.
Magisk Stable
Magisk Manager v7.1.1
Magisk v18.1
Full Changelog link: https://dwnld.aicp-rom.com/
(Just click the changelog button next to the download link in the list of builds available for your device)
You tell...
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look in the OP to see if your device is built on a nightly or weekly schedule.
Q. Does this ROM support custom kernels officially?
A. No. You can still use them, but discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Why doesn't this ROM support Xposed?
A. Xposed is a hack that is geared towards AOSP. Custom ROMs modify the framework a lot, so Xposed can cause a ton of issues on custom ROMs. Now it might work for you, however it is not to be discussed in this thread, and you should refrain from posting bug reports.
Q. Alright, but I still want to flash Xposed, so which version do I need to install?
A. You will need to use the version arm64/arm/whatever for SDK 28.
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the install instructions in the first post...
Q. Can the builds be dirty flashed over each other?
A. Yes, however make a nandroid backup first as there is a chance of getting a bootloop or encountering bugs. Also bugs may only be reported on a clean flash.
Q. How do I 'dirty flash' builds?
A. Wipe the System, Cache and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), your preferred root solution and reboot. Or just use the OTA app to preform that task for you.
Q. How do I flash kernel builds?
A1. If it's a .img file, boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot" as the destination, then swipe to flash, then go back to the install screen and install your root method again, if you don't want to loose root and reboot.
A2. If it's a flashable ZIP, you can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to loose root. Now swipe to flash and reboot afterwards.
Using the ROM:
Q. I installed a bad theme and now I'm getting a bootloop, how do I fix it?
A. In TWRP, flash the substratum rescue zip that's in the substratum folder on the internal storage.
Q. I'm having issues with WhatsApp, how do I fix it?
A. Read this
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat. (Note: Please just link the logcat from your GDrive, Dropbox, etc. and do not post the content here. Thanks.)
Q. How do I get a logcat, what type should I get and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (Root needed).
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the others section in the AICP Extras main page.
The ROM should contain everything you need to enjoy Android Pie. You don't need to install any Add-on's, simply download the latest ROM, GApps, flash it and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM Zipfile.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup as this can cause stability issues that are very hard to debug.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash for the first time:
(Again: Don't do it if you don't know it!)
1. Download the ROM and GApps and transfer them to your device.
2. Boot to recovery (TWRP recommended).
3. Wipe the System, Cache, and Data (you might need to format the data partition!).
4. Flash the ROM Zipfile.
5. Flash the GApps (optional, needed for e.g. Google Playstore to work).
6. Reboot and set up your device, enable developer settings and in them OEM unlock/Advanced reboot/USB tethering.
7. Reboot back into TWRP recovery.
8. Flash the root solution of your choice (optional).
9. Reboot your device.
The procedure might vary from device to device and is a bit different on system updates!
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once! This might differ on AvB Devices.
The root solution can be flashed together with every OTA update (= ROM Update).
PREREQUISITE FOR OTA ("Over-The-Air" Updates):
To be able to flash using the built-in OTA app, TWRP recovery is needed.
Please be sure that you are on the latest TWRP recovery. Keep in mind that this could also be an unofficial version!
On encrypted devices you will have to enter your PIN/password in TWRP before the process starts.
If you want to contribute to the AICP or want see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Kernel source:
apq8084 Kernel
Telegram:
Note 4 SnapDragon ROM Testers
TWRP:
TWRP XDA Thread
ROM & Additional links:
AICP's Homepage
AICP Gerrit Code Review
AICP sources on Github
AICP Download page for official builds and media content
AICP Discord Community​
XDA:DevDB Information
[Unofficial] AICP 14, ROM for the Samsung Galaxy Note 4
Contributors
Shizzle2889, Inkypen, TripLr, _mone, mobspyguy, cvxda, ripee
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Testing
Created 2019-04-07
Last Updated 2019-06-29
roomservice.xml
To my knowledge, these room service files should be stable. Please let us know if any are not. Easiest way to do so is via the Telegram group linked at (near) bottom of OP for testing ROMs, but more than welcome here as well. Thank you.
TRLTE:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="AICP/packages_apps_FlipFlap" path="packages/apps/FlipFlap" remote="github" revision="p9.0" />
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_hardware_sony_timekeep" path="hardware/sony/timekeep" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_kernel_samsung_apq8084" path="kernel/samsung/apq8084" remote="github" revision="lineage-16.0" />
<project name="triplr-dev/android_device_samsung_apq8084-common" path="device/samsung/apq8084-common" remote="github" revision="aicp-p9.0" />
<project name="triplr-dev/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="lineage-16.0" />
<project name="triplr-dev/android_device_samsung_trlte" path="device/samsung/trlte" remote="github" revision="aicp-p9.0" />
<project name="triplr-dev/android_device_samsung_trlte-common" path="device/samsung/trlte-common" remote="github" revision="aicp-p9.0" />
<project name="triplr-dev/android_hardware_samsung" path="hardware/samsung" remote="github" revision="aicp-p9.0" />
<project name="triplr-dev/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="lineage-16.0" />
</manifest>
TBLTE:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="AICP/packages_apps_FlipFlap" path="packages/apps/FlipFlap" remote="github" revision="p9.0" />
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_hardware_sony_timekeep" path="hardware/sony/timekeep" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_kernel_samsung_apq8084" path="kernel/samsung/apq8084" remote="github" revision="lineage-16.0" />
<project name="triplr-dev/android_device_samsung_apq8084-common" path="device/samsung/apq8084-common" remote="github" revision="lineage-16.0" />
<project name="triplr-dev/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="lineage-16.0" />
<project name="triplr-dev/android_device_samsung_tblte" path="device/samsung/tblte" remote="github" revision="aicp-p9.0" />
<project name="triplr-dev/android_device_samsung_trlte-common" path="device/samsung/trlte-common" remote="github" revision="aicp-p9.0" />
<project name="triplr-dev/android_hardware_samsung" path="hardware/samsung" remote="github" revision="aicp-p9.0" />
<project name="triplr-dev/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="lineage-16.0" />
</manifest>
TRLTEDuos:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="AICP/packages_apps_FlipFlap" path="packages/apps/FlipFlap" remote="github" revision="p9.0" />
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_hardware_sony_timekeep" path="hardware/sony/timekeep" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_kernel_samsung_apq8084" path="kernel/samsung/apq8084" remote="github" revision="lineage-16.0" />
<project name="triplr-dev/android_device_samsung_apq8084-common" path="device/samsung/apq8084-common" remote="github" revision="lineage-16.0" />
<project name="triplr-dev/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="lineage-16.0" />
<project name="triplr-dev/android_device_samsung_trlteduos" path="device/samsung/trlteduos" remote="github" revision="aicp-p9.0" />
<project name="triplr-dev/android_device_samsung_trlte-common" path="device/samsung/trlte-common" remote="github" revision="aicp-p9.0" />
<project name="triplr-dev/android_hardware_samsung" path="hardware/samsung" remote="github" revision="aicp-p9.0" />
<project name="triplr-dev/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="lineage-16.0" />
</manifest>
Reserved
ROM Download links are now up. Currently uploading. Once up, you should be able to check them out. Let us know what issues you guys and gals run into, and please let us know the specific device you have the issue on. Thank you, just be aware there has been no extensive testing done yet on any of these.
1 rst,
Too many thankd for this new release...
amazing.
:good:
Amazing i been waiting for this long time ago , thanks so much ?
I managed to do the Pie bringup but I don't actually own the device, so please PLEASE supply a logcat if you have any problems or issues. Setting up ADB is beyond the scope of this thread, so If you don't know how to get the logs there are plenty of online guides for doing so.
Inkypen said:
I managed to do the Pie bringup but I don't actually own the device, so please PLEASE supply a logcat if you have any problems or issues. Setting up ADB is beyond the scope of this thread, so If you don't know how to get the logs there are plenty of online guides for doing so.
Click to expand...
Click to collapse
And I just did a restore. Sigh
Someone can upload some screenshots, pls
Thanks for your hard work as developers, you're the best <3
Further the AICP logo isn't established.
tripLr said:
And I just did a restore. Sigh
Click to expand...
Click to collapse
Lol, you poor bugger
i know that pain so well
You're like me, no...worse, must be suffering from serious flash fatigue
so i have bootloop still 30min.Clean install,everything wipe.SM N910F
here no booting too. Clean install, tried even with new TWRP 323.1 update. No sucess
my device N910F
Sofar no boot. Stuck at animation. Dmsg posted in telegram
scpeter1 said:
so i have bootloop still 30min.Clean install,everything wipe.SM N910F
Click to expand...
Click to collapse
Same for me SM N910F
when flashing the rom does not start and stays in the acip logo and does not start. I have done a clean installation and it stays in a bootloop. I have a sm910f
Enviado desde mi SM-N910F mediante Tapatalk
If someone can get an adb logcat while stuck in boot animation @Inkypen 's instructions
When on bootscreen, connect to computer and type "adb logcat >logcat.txt" then after a few secs ctrl-c to get your command prompt back. Send that log to me ?
Then you can copy it to your computer via adb shell I believe.
Test build for trlte, need feedback if it boots. https://drive.google.com/open?id=17tzeTHKqJnhJ0z7d-AgOsh6l79lkR9Kd
Still boot looping
Sorry to report that it still is boot looping.
N910V Note 4
scpeter1 said:
so i have bootloop still 30min.Clean install,everything wipe.SM N910F
Click to expand...
Click to collapse
Same for my N910T :c
I tried version from 8.4 and I have still bootloop.
Odoslané z LYA-L29 pomocou Tapatalku

[ROM][UNOFFICIAL] LineageOS 20.0 for Nexus 6

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
lineage-20.0-20230222-UNOFFICIAL-shamu.zip
lineage-20.0-20221217-UNOFFICIAL-shamu.zip
lineage-20.0-20221014-UNOFFICIAL-shamu.zip
Known issues:
- On some boots the camera may not be working. Simply reboot your phone to fix it.
How to enable encryption on the February build and newer:
- Data must be formatted. If you're using TWRP, click wipe and then format data
- Install the LineageOS zip
- Install the attached SetEncryption.zip
- Reboot and enjoy encryption
How to build from source:
I'm going to assume you've built LineageOS before and just describe the special steps
- Repo init with the LineageOS-UL sources here: https://github.com/LineageOS-UL/android
- Copy the attached roomservice.xml to .repo/local_manifests
- Sync the sources
- From the source root execute:
Code:
sed -i "s/.*TARGET_BUILD_UNBUNDLED.*/ifeq (0,1)/" build/make/core/tasks/platform_availability_check.mk
- If you want your builds to use encryption then run:
Code:
sed -i "s/latemount/latemount,fileencryption=adiantum/" device/moto/shamu/rootdir/etc/fstab.shamu
- cd to frameworks/opt/net/ims and run git apply path_to_attached_Ignore-SubId.patch
- DO NOT use an existing vendor repo . You must run ./extract-files.sh on the latest build I've provided
- Build as normal
Kernel Source: https://github.com/rootfan/android_kernel_moto_shamu
Special thanks to:
- LineageOS team
- Elektroschmock, npjohnson, and anyone else who has worked on shamu in the past
- abhishekt295 and wavedashdoc for getting IMS to work on android 10
- tarkzim and khalvat for their work on the LineageOS-UL project
Standard disclaimer: You're responsible for what you do to your devices, so don't blame anyone else if something goes wrong.
Enjoy android 13 on the Nexus 6
bravo!!!!!!!
any build plan for angler?
Which gapps to use with this build?
Hey, I'm here to do some reports.
My last OS is Mokee based on Oreo 8.1 and I flashed this from with TWRP 3.1.1-0.
When the first time I try to flash it notices that "This package is for shamu, and your device is [empty]." So I removed the asserts check from update-script and I made it this time.
Here are my steps to flash this:
1. Reboot into recovery, wipe data.
2. Wipe data, davlik, system, data, and cache.
3. Flash the rom
4. Format data
5. Reboot
Now it is stuck in the loop of lineage os boot animation. Any suggestions?
I happen to come across this thread and just had to poke my head in here real quick and say "hell yeah! ' " Long live the Nexus!! "I always like it when I see a Nexus still getting current rom love. I had all of the Nexus devices.
Those were the days!!
lepi said:
Which gapps to use with this build?
Click to expand...
Click to collapse
I used BiTGApps-arm-13.0.0-v1.4_signed.zip. I did dirty flash to lineage-19.1-20220919-UNOFFICIAL-shamu. lineage-20.0 booted without any problem.
MindTheGapps-13.0.0-arm-20221007_211145.zip may be used instead.
TatsuMasa said:
I used BiTGApps-arm-13.0.0-v1.4_signed.zip. I did dirty flash to lineage-19.1-20220919-UNOFFICIAL-shamu. lineage-20.0 booted without any problem.
MindTheGapps-13.0.0-arm-20221007_211145.zip may be used instead.
Click to expand...
Click to collapse
Used MindTheGapps 13, thanks
Thanks a lot! Great work!
the camera is not working, please tell me how to fix it
bccrosby said:
the camera is not working, please tell me how to fix it
Click to expand...
Click to collapse
Be patient. Release 20.0 is very early. Take a look at >chengelog<. Work continues, including on the camera.
bccrosby said:
the camera is not working, please tell me how to fix it
Click to expand...
Click to collapse
Just reboot your phone and then the camera should work fine.
rootfan said:
Just reboot your phone and then the camera should work fine.
Click to expand...
Click to collapse
thank you for android 13 on the nexus 6 although the play store cant update apps because it doesnt have a storage permission
for some reason
@rootfan
Thanks for your work !
I was feeling adventurous this morning so I tried to build with your repos
To do so I've gotten to adding the following lines to my roomservice.xml
XML:
<project path="kernel/moto/shamu" remote="github" name="rootfan/android_kernel_moto_shamu" revision="los-20.0" />
<project path="device/moto/shamu" remote="github" name="rootfan/android_device_moto_shamu" revision="los-20.0" />
<project path="vendor/motorola" remote="github" name="TheMuppets/proprietary_vendor_motorola" revision="lineage-18.1" />
<project name="LineageOS/android_hardware_sony_timekeep" path="hardware/sony/timekeep" revision="lineage-18.1" />
but build is failing with
Code:
FAILED:
build/make/core/main.mk:1308: warning: device/moto/shamu/lineage_shamu.mk includes non-existent modules in PRODUCT_PACKAGES
Offending entries:
nfc_nci.bcm2079x.default
build/make/core/main.mk:1308: error: Build failed.
12:15:32 ckati failed with: exit status 1
--> What am I missing ?
I noticed you also have a android_frameworks_opt_telephony repo, but I have not used it as your initial post suggests only kernel source and device tree repos are necessary. --> Is it also required ?
Lastly, do you plan on merging the shamu: Kang DRM from angler commit that make NEtflix work again !
Looking forward to testing this on my shamu
dwardo said:
@rootfan
Thanks for your work !
I was feeling adventurous this morning so I tried to build with your repos
To do so I've gotten to adding the following lines to my roomservice.xml
XML:
<project path="kernel/moto/shamu" remote="github" name="rootfan/android_kernel_moto_shamu" revision="los-20.0" />
<project path="device/moto/shamu" remote="github" name="rootfan/android_device_moto_shamu" revision="los-20.0" />
<project path="vendor/motorola" remote="github" name="TheMuppets/proprietary_vendor_motorola" revision="lineage-18.1" />
<project name="LineageOS/android_hardware_sony_timekeep" path="hardware/sony/timekeep" revision="lineage-18.1" />
but build is failing with
Code:
FAILED:
build/make/core/main.mk:1308: warning: device/moto/shamu/lineage_shamu.mk includes non-existent modules in PRODUCT_PACKAGES
Offending entries:
nfc_nci.bcm2079x.default
build/make/core/main.mk:1308: error: Build failed.
12:15:32 ckati failed with: exit status 1
--> What am I missing ?
I noticed you also have a android_frameworks_opt_telephony repo, but I have not used it as your initial post suggests only kernel source and device tree repos are necessary. --> Is it also required ?
Lastly, do you plan on merging the shamu: Kang DRM from angler commit that make NEtflix work again !
Looking forward to testing this on my shamu
Click to expand...
Click to collapse
Try to track this in your manifests, maybe it will work.
GitHub - LineageOS/android_hardware_broadcom_nfc
Contribute to LineageOS/android_hardware_broadcom_nfc development by creating an account on GitHub.
github.com
Furthermore,resync @rootfan 's repos for 20.0 branch when he make it up-to-date.
Can someone kindly confirm GPS works on this build? I have LinOS 20 on another phone (admittedly an ancient Sams. Note 2) and the GPS works but very sluggish. All else works fairly well.
On my Nexus 6, I have the well-cared for LinOS 18.1 and GPS is very quick- the whole ROM is rock solid. I can of course make a recovery copy but just want to know what to expect as this is still my daily driver. Some of the rebooting & charging issues also make me a bit uneasy. I know it is still early days and am only grateful for rootfan's efforts.
What have any of you lab rats (just kidding) experienced so far specifically regarding GPS with this 20 ROM on a nav map system e.g. Organic or Google Maps? Thanks
TotalChen said:
Try to track this in your manifests, maybe it will work.
GitHub - LineageOS/android_hardware_broadcom_nfc
Contribute to LineageOS/android_hardware_broadcom_nfc development by creating an account on GitHub.
github.com
Furthermore,resync @rootfan 's repos for 20.0 branch when he make it up-to-date.
Click to expand...
Click to collapse
That got me to the next issues .
tons of warnings turned to errors (found how to bypass that) as -Werror compile option is set
kernel includes not found by other projects
Seems rootfan's modification's are not up to date or all available on his github. Will check from time to time and see if updates become available.
Took the plunge as I can quickly and easily revert back to rock solid LOS18 if nec. with TWRP backup. So..
Unlocked phone and SIM card, dirty flashed ROM, BitGaps 1.6, Magisk 24.3s.....
Whole installation, a few reboots, some App checking, took like 10 Min. Dirty flash saves hours of re-confiuring and reinstalling files and apps. YMMV but as I am fully backed up, it was well worth a try.
All seems just fine. Banking apps, travel, cars etc. all good. My Open Camera app, and the built in Camera all sans problems. Even kept some deep Magisk modules. Will have to watch for a few days re GPS, notifications, battery life. It is slightly less smooth than LOS18 but can easily live with it, and it may improve over time. Have asked trusted wingman to also try and monitor.
@rootfan Nice one; hope you'll keep supporting and updating this great work.
Thank you @rootfan for bringing new up to date life to Shamu . Really amazing to see android 13 on it !
Just a heads-up. Reporting, not complaining.
I followed @esysfound in dirty flashing my N6, and it looked good, but today I've booted from cold and I'm in a bootloop - the LOS circles have been running for a while with occasional reboots. No problem - (a) I knew dirty flashing isn't reliable and (b) I can restore my OrangeFox 19.1 backup.
Just in case anyone is thinking of trying a dirty flash...

Categories

Resources