{
"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"
}
Device: m7 (HTC One)
All I've done is compiled sources to bring you these builds. All the heavy lifting is done over at https://github.com/htc-msm8960 - thank those guys, they are working incredibly hard to bring AOSP to this device. I think the list of developers goes something like this: h8rift, intervigil, toastcfh, deck, Flinny, Flemmard, Codeworkx, birdman
That means that any bugs that exist in other AOSP builds will probablacy exist in these builds.
Click to expand...
Click to collapse
» Installation is simple:
If coming from another ROM or another major AOKP version, wipe data in recovery
Make sure you're using the latest CWM or TWRP
Flash ROM
Flash Google Apps (GAPPS)
Reboot
Code:
May 22
- included test call audio fix
- included xxhdpi device commits
May 21
- latest AOKP sources
- latest CM m7 sources
from gerrit:
- updated ribbons
- LockScreen: Fix crash when unlocking twice
- Add transparency settings for lockscreen (2/2)
- Smooth Spinners: Makes the loading "spinner" animation smoother in non-holo apps
sorry for the delay for those who waited :)
» Check merged commits on AOKP's Gerrit
build: http://goo.im/devs/roman/aokp_m7 - my nightlies will be in this folder. I'll also probably push them through AOKPush
gapps: http://goo.im/gapps/gapps-jb-20130301-signed.zip - b7e53e96e1c8b1a1c4865bf29418c8e0
» Building AOKP for your m7
First, create file .repo/local_manifests/m7.xml with the following contents: https://gist.github.com/romanbb/5517890
repo sync
Cherry pick this: http://gerrit.aokp.co/#/c/8320/
Cherry pick this: http://gerrit.aokp.co/#/c/8159/
Cherry pick this: http://gerrit.aokp.co/#/c/8321/
Build aokp_m7:
Code:
. build/envsetup.sh && brunch aokp_m7-userdebug
» AOKP Gerrit
» AOKP on Github
» SOURCE on AOKP.co
We greatly appreciate your contribution in the form of code, or PayPal donations.
» Donation options on AOKP.co
Enjoy!
for science
Whhhhhhhat?!?!?! Awesome sauce, great to see you here Roman!!
Did you get the one Roman? My wife got it and I'm debating selling my s3 for it. Any thoughts on the phone or are you gonna dev for it? Thanks
Sent from my SGH-T999 using Tapatalk 2
eliasadrian said:
Did you get the one Roman? My wife got it and I'm debating selling my s3 for it. Any thoughts on the phone or are you gonna dev for it? Thanks
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
He's got the HTC One on T-Mobile
https://twitter.com/romanbb/status/330053433702887425
eliasadrian said:
Did you get the one Roman? My wife got it and I'm debating selling my s3 for it. Any thoughts on the phone or are you gonna dev for it? Thanks
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, Amazon hardware. I'm not going to dev so much "for" it, even though I might try... but I think I'll dev with it?
Sent from my Nexus 7 using Tapatalk HD
new build up http://goo.im/devs/roman/aokp_m7/
coming from the s3, any word on what works and what does not work?
nicksmizzle said:
coming from the s3, any word on what works and what does not work?
Click to expand...
Click to collapse
Camera doesn't work
Sent from my HTC One using xda app-developers app
Camera Bummer
Once camera works, this will be my daily driver! can hardly wait!!!:highfive:
Roman,
Good to see you around, I think something is up with AOSP with the GFX. If you download the live wallpaper below you will see it has some strange effects that do not happen on the stock rom. My Nexus 10 tablet on 4.2.2 does not have the artifacts so I do not believe this is a 4.2.2 issue with the phone but both your rom and the ALPHA for Cyanogen 10.1 both display the issue.
https://play.google.com/store/apps/details?id=com.tribok.android.livewallpaper.springtideshower.lite
Its a great wallpaper BTW but wanted to bring it to your attention because maybe something is off with the GFX driver being used? I understand that major work is done by https://github.com/htc-msm8960 but thought I would let you know if you could help pass along.
Thanks,
1WayJonny
Roman, good to have you on the one.
I sure hope you all can get the camera working....
I get this on compiling from the new .xml and instructions today
device/htc/m7-common/overlay/packages/apps/Settings/res/values/arrays.xml:8: error: Error: No resource found that matches the given name (at '^index_0' with value '@string/pulse_length_always_on').
make: *** [/home/joey/aokp/out/target/common/obj/APPS/Settings_intermediates/src/R.stamp] Error 1
make: *** Waiting for unfinished jobs....
warning: no entries written for dimen/password_keyboard_height
warning: no entries written for drawable/sym_keyboard_delete_holo
any suggestions?
superg81 said:
I get this on compiling from the new .xml and instructions today
device/htc/m7-common/overlay/packages/apps/Settings/res/values/arrays.xml:8: error: Error: No resource found that matches the given name (at '^index_0' with value '@string/pulse_length_always_on').
make: *** [/home/joey/aokp/out/target/common/obj/APPS/Settings_intermediates/src/R.stamp] Error 1
make: *** Waiting for unfinished jobs....
warning: no entries written for dimen/password_keyboard_height
warning: no entries written for drawable/sym_keyboard_delete_holo
any suggestions?
Click to expand...
Click to collapse
check the op. there are new build instructions. it's specifically the overlay commit that will fix that for you
Romanbb said:
check the op. there are new build instructions. it's specifically the overlay commit that will fix that for you
Click to expand...
Click to collapse
just did and get this now
From http://gerrit.aokp.co/AOKP/device_htc_m7-common
* branch refs/changes/81/8481/1 -> FETCH_HEAD
error: Your local changes to the following files would be overwritten by merge:
overlay/frameworks/base/core/res/res/values/config.xml
Please, commit your changes or stash them before you can merge.
Aborting
let me re post here
From http://gerrit.aokp.co/AOKP/device_htc_m7-common
* branch refs/changes/20/8320/4 -> FETCH_HEAD
error: Your local changes to the following files would be overwritten by merge:
overlay/frameworks/base/core/res/res/values/config.xml
Please, commit your changes or stash them before you can merge.
Aborting
superg81 said:
just did and get this now
From http://gerrit.aokp.co/AOKP/device_htc_m7-common
* branch refs/changes/81/8481/1 -> FETCH_HEAD
error: Your local changes to the following files would be overwritten by merge:
overlay/frameworks/base/core/res/res/values/config.xml
Please, commit your changes or stash them before you can merge.
Aborting
let me re post here
From http://gerrit.aokp.co/AOKP/device_htc_m7-common
* branch refs/changes/20/8320/4 -> FETCH_HEAD
error: Your local changes to the following files would be overwritten by merge:
overlay/frameworks/base/core/res/res/values/config.xml
Please, commit your changes or stash them before you can merge.
Aborting
Click to expand...
Click to collapse
in each of those dirs, you could do a "git reset --hard HEAD" to clear out any changes you may have made
Romanbb said:
in each of those dirs, you could do a "git reset --hard HEAD" to clear out any changes you may have made
Click to expand...
Click to collapse
gotcha,shall try that
did you realize 4 and 5 in op for picks are same?
superg81 said:
gotcha,shall try that
did you realize 4 and 5 in op for picks are same?
Click to expand...
Click to collapse
i did not
Romanbb said:
i did not
Click to expand...
Click to collapse
:silly:
are you guys using the tmo htc one having any issues with call audio?
Related
{
"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"
}
Those are UNOFFICIAL BUILDS, use at your own risk.
Please let me know if this helps anyway =)
LATEST BUILD:
All builds are available on:
http://xfer.in/pier and
http://goo.im/devs/pier
31 Aug - M6+ (ICS) - aokp_galaxys2_pier_M6plus.zip - md5: 99c06552680c586276aa61e96e1a209f
Code:
Changelog:
Project name: proprietary_vendor_samsung
•chris41g - rename to d710 per other SGSII variants
•Koushik Dutta - fix herp derp
•chris41g - permissions
Project name: packages_apps_Camera
•Ricardo Cerqueira - Camera: Prevent double-stops on preview for some HALs
•Pierpaolo Pernici - camera: ISO support from CM7 (2/2)
Project name: platform_manifest
•Pierpaolo Pernici - Tracking CM zlib to fix recovery build (fopen64)
Project name: android_bootable_recovery
•Daniel Bateman - recovery: fix up key repeating
•Koushik Dutta - 6.0.1.2
•Koushik Dutta - First pass at fixing up the threading issues in ro.cwm.enable_key_repeat.
•David Ferguson - recovery: support for more than 1 sdcard in USB mass storage
Project name: device_samsung_galaxys2
•Pierpaolo Pernici - upd
Project name: platform_manifest
•Pierpaolo Pernici - Tracking CM zlib to fix recovery build (fopen64)
Project name: frameworks_base
•rodries - Fix compiling errors in AudioService.java
•Phil Tunstall - Fix ring/notification volume not restoring correctly on headset (dis)connect
•Phil Tunstall - Sound preference: Safe volume restore when plugging in a headset (1/2)
•Phil Tunstall - Fix ring/notification volume not restoring correctly on headset (dis)connect
•codeworkx - Smdk4210RIL: swap voice privacy and video
•Emilio López - Turn off "too slow" logs.
•codeworkx - camera: fix samsung/qcom conflict
23 Jul - CM9/AOKP KERNEL - kernel-cm-9-20120723-galaxys2-signed.zip - md5 efb12d05b7313e9821c5be1a866d09a3
GAPPS, for the lazy ppl:
MD5: 7c524e1e078164f681e0aa6753180b2c
Link: http://goo.im/gapps/gapps-ics-20120429-signed.zip
Misc stuff:
Apollo.apk - CM's music player
FileManager.apk
Older builds archive: > HERE <
FAQ:
If you do not have the date in the notification bar, go into Settings -> ROM Control -> Weather and enable it (Enable Weather must be ticked). If for whatever reason you do not want weather integration, just toggle it on and off. Date will be shown in the notification bar even with the weather disabled, but only if it has been enabled previously. (thx CX)
INFO and Credits:
My AOKP github: https://github.com/pierpp
Looking for me? come to Freenode IRC on channel #AOKP-SGS2
THANKS AND CREDITS TO:
- AOKP and CyanogenMod Crews
- Sixstringsg, Xplodwild, Snipa, Codeworkx
- Bajee11, Rodries and the "real" SGS2 developers
SUPER SPECIAL THANKS TO MY SUPPORTERS!
- john3166
CLICK THAT F/&%&"$ THANKS BUTTON!!!! :angel:
Thanks for your effort. So far, so good.
no feedbacks yet?
mine works ok
just asking how do u revert a commit ?
I used:
Code:
git reset <shaid> --hard
PieR said:
I used:
Code:
git reset <shaid> --hard
Click to expand...
Click to collapse
You can also do "git revert" - This will JUST revert the commit, and put it in the changelog as a revert, instead of rewinding the repo.
Thanks for finding the likely culprits, I'll test and if it fixes things for me, I'll gerrit reverts tonight.
Did you try reverting either of these independently?
Codeworkx smells something about libcutils, so I'll start to revert only this one
PieR said:
Codeworkx smells something about libcutils, so I'll start to revert only this one
Click to expand...
Click to collapse
Yeah, that has a whole pile of network functionality, which would jive with network being wonky.
compiling.. 30 mins to go now
Should I use CCACHE?
PieR said:
compiling.. 30 mins to go now
Should I use CCACHE?
Click to expand...
Click to collapse
ccache rocks, but making/reverting changes to certain parts of the code just automatically forces a big change.
Will test on n7000 in about an hour.
this one:
Revert "libcutils: Fix aliasing violations"
This reverts commit a63c4f18f2400fd05ecd1cee88199c32477297d4.
seems NOT to be a fix.
going to try the other one alone now.
http://review.cyanogenmod.com/#/c/17773/
Revert "libcore: Fix aliasing violations"
This reverts commit 37467534830c84a56279769b8aa03115540f7121.
This commit broke Foursquare, Tweetdeck, Voxer, and Instagram
Probably other apps too.
The general theme is that they are unable to sync network
feeds or lists.
Click to expand...
Click to collapse
THANKS TO dev ENTROPY512 FOR HIS SUPPORT!
PieR said:
http://review.cyanogenmod.com/#/c/17773/
THANKS TO dev ENTROPY512 FOR HIS SUPPORT!
Click to expand...
Click to collapse
I'm building this to test on Maguro now, since people with that device are also reporting this issue, I'll comment on Gerrit if nothing adverse happens.
Added a new build with only the proper fix.
This thread will self-destruct as soon as they will merge the commit
PieR said:
Added a new build with only the proper fix.
This thread will self-destruct as soon as they will merge the commit
Click to expand...
Click to collapse
Might wanna try to explain the main problem to Arcee on Gerrit, he wants more info on how this breaks Foursquare, etc...
He's likely going to be the one to do the final sign off, so if you want it fixed fast, convincing him would be a good idea
This is of no use to me since I don't use any of those apps but I really appreciate your work. I do remember using one of your nightly builds when BOT was down
Good job PIER helping the community. You can keep sharing your kangs of nightlies. Thanks once again
Sent from my Galaxy S2 powered by CM9
Yes your nightlies are awesome please share them.
Well done, thanks for finding the fault and fixing it. Hope this gets committed soon.
thracemerin said:
Might wanna try to explain the main problem to Arcee on Gerrit, he wants more info on how this breaks Foursquare, etc...
He's likely going to be the one to do the final sign off, so if you want it fixed fast, convincing him would be a good idea
Click to expand...
Click to collapse
Sry I was sleeping
I'll keep an eye on gerrit: it looks you guys moved forward!
Atm I'm rebuilding with patchset 2
New build UP on the OP
[TUTORIAL] 【GUIDE】【LINARO】《《How to Build FULL LINARO》》【06/05/13】
{
"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"
}
Welcome! This thread will teach you how to correctly build AOSP Roms for the HTC Rezound using the Linaro toolchains or other 4.8+ toolchains.
***PLEASE NOTE*** You must already have a knowledge of building roms before attempting this. This is not a how to build rom thread.
Thanks goes out to XDA Recognized Contributor DJLamontagneIII for helping me to learn how to do this, and for helping me resolve some conflicts along the way! I could not have done it without you sir. Thanks!
Additionally, thanks goes out to Recognized Developer sparksco aka "SaberMod" for the use of his optimized tool chains and for teaching me and helping me along the way.
Thanks also goes out to Flyhalf205 for coming on board with this mission and working with me to make this possible for everyone else to build.
PLEASE NOTE:
I or the above mentioned or anyone else for that matter am/are not responsible for anything you do to your phone.
That being said, let's begin
Recently, I have come up with a major simplified way of achieving this goal. for those who are interested in the intricate details of what all goes into this lengthy process and just how much time my script is actually saving you, it will be in a hidden window near the end of this post.
(Remember again, that these instructions are for individuals how have already compiled a rom and are certain their current source builds)
Fetch the script.
Do that by typing one of the three following from your root directory:
Code:
THIS IS BEING UPDATED. ONCE UPDATED, THE FOLLOWING THREE OPTIONS WILL BE AVAILABLE TO YOU:
linaro.sh
saber.sh
codefire.sh
then do:
Code:
. script-you-chose.sh
This script that I've put together is incredibly convenient in that it will do all of the following tasking essentials that you would normally have to do manually for you automatically (which would normally take a good deal of time!)
-Pulls the optimized chain of choice and places it into prebuilts/gcc/linux-x86/arm
-Pulls other optimized chains from google source as well
-Modifies your build repo and a few other build files to direct it to the new chain
-Pulls about 32 different linaro patches and optimizations made by the linaro team that improve the performance of the rom
-modifies whichever kernel you are currently building with to allow it to build Linaro
-Modifies our device specific repos to allow it to build with the linaro chain
-Sets the building variables
-Fetches your vendor prebuilts
-Builds your envsetup.sh for you
Any questions or concerns or need for assistance? Please post in this thread and we will be happy to assist you when available (and if we know how to fix it)
Donations are always appreciated and never expected!
Mine: https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=ER36WF5HCHTEU
sparksco's: http://forum.xda-developers.com/donatetome.php?u=2394329
DJLamontagneIII's: http://forum.xda-developers.com/donatetome.php?u=1249390
FlyHalf's: http://forum.xda-developers.com/donatetome.php?u=3082717
One more for kicks
You will have to run ". android/linaro.sh" again after you perform a "repo sync". It will discard those Linaro commits.
thank you guys very much:thumbup:
Sent from my HTC Rezound using xda premium
Very nice!
Sent from my XenonHD Infused Samsung Galaxy s3 using xda premium
Sweet!
I just built yesterday, so I know everything works...
Tried again after a fresh repo sync and running linaro.sh
Code:
/home/vwmofo/android/MofoROM-2.0/kernel/htc/vigor-3.0/drivers/base/sync.c:32:31: fatal error: trace/events/sync.h: No such file or directory
compilation terminated.
make[4]: *** [drivers/base/sync.o] Error 1
make[3]: *** [drivers/base] Error 2
make[2]: *** [drivers] Error 2
make[2]: *** Waiting for unfinished jobs....
then a little further down
Code:
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/home/vwmofo/android/MofoROM-2.0/kernel/htc/vigor-3.0'
make: *** [TARGET_KERNEL_BINARIES] Error 2
Try another repo sync and run linaro script again. I made some kennel commits last night. Make sure you get those
Sent from my ADR6425LVW using Tapatalk 2
@kkozma, is that with the default kernel from fly's git or someone else's?
If it's with funky kernel from the jb-aosp branch, then you don't need to do the kernel commit part of the script as his is linaro ready
It's the default kernel.
I just ran a new repo sync and there were no changes other than the removal of all the commits from the script. Re-ran the script and started up a brunch.
But considering nothing new was downloaded, I don't think it's going to work.
*edit* I did clobber and clean before the build the first time.
If it crashes again, revert all of yesterday's commits to the kernel except for the linaro commit and see if it builds then. You will have to do a make clean obviously after the crash just as you just did
kkozma said:
It's the default kernel.
I just ran a new repo sync and there were no changes other than the removal of all the commits from the script. Re-ran the script and started up a brunch.
But considering nothing new was downloaded, I don't think it's going to work.
*edit* I did clobber and clean before the build the first time.
Click to expand...
Click to collapse
repo sync again right now.... I might have forgotten a commit.
DOH! Ok, I killed the last build, and re-ran repo sync. It did download something from your github.
It's brunching now. Will report back.
kkozma said:
DOH! Ok, I killed the last build, and re-ran repo sync. It did download something from your github.
It's brunching now. Will report back.
Click to expand...
Click to collapse
My bad. If it errors out one more time. Just do a another repo sync. My box didn't push all my commits. Really weird. But all should be pushed now. As of 1 minute ago.
So we're all bubble gum and kittens again?
Sent from my HTC One X using Tapatalk 4 Beta
IAmTheOneTheyCallNeo said:
So we're all bubble gum and kittens again?
Sent from my HTC One X using Tapatalk 4 Beta
Click to expand...
Click to collapse
You got it dude!
FYI: It built.
Running backups now and will be flashing soon.
kkozma said:
FYI: It built.
Running backups now and will be flashing soon.
Click to expand...
Click to collapse
Glad to know the script works In the future, I plan to add more linaro patches to it along with eventually updating us to linaro 4.9 which has been reported much faster than the previous chains
SAMSUNG GALAXY NEXUS (Tuna) Support
I just finished putting together a script specifically for the Samsung Galaxy Nexus AOKP building and can confirm that it works beautifully.
In case any of you out there build for that device. I gave it to Apophis if you need it
-Neo
IAmTheOneTheyCallNeo said:
Glad to know the script works In the future, I plan to add more linaro patches to it along with eventually updating us to linaro 4.9 which has been reported much faster than the previous chains
Click to expand...
Click to collapse
Yeah, seems like it works great. My phone definitely seems more responsive too.
Hopefully the RR's are fixed since my last build.
{
"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"
}
DISCLAMER
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.
Click to expand...
Click to collapse
LiquidSmooth is an aftermarket firmware based on the Android Open Source Project.
Dedicated to providing users with smooth, stable and fast ROMs. A Lightweight modified AOSP base, and then add the features you crave!
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device.
We ask that you do your part to know your device and know how to recover from problems before you flash!
Liquid0624
Deadman96385
jsnweitzel
Somber73
TheBr0ken
CPA-Poke
Cdub50
Code:
Linaro 4.9 GCC Toolchain
O3 Strict-Aliasing & ISO C++11 Mode
ARM Optimized String Handling Routines
Linaro and Code Aurora Optimaztions
Slims DPI on the fly
Custom animation controls
TRDS 3.0 (Liquid Blackout in settings)
Active Display
Slims QuickSettings
Halo (Renamed to bubble in settings)
Ram Bar
CM Theme Engine
Privacy Guard
Built in SuperUser
Working wifi Tethering
Cell Broadcasts
Slims Configurable Power Menu
Slims Configurable Nav Bar
Custom animation controls (Listview)
LockScreen Notifications
And way more than this...
Code:
[url="https://plus.google.com/b/102153960718796996774/communities/117452480298315341829/stream/d5e8c0fe-5ee7-44df-97a5-6dd8cdcf8bb8"]Check are Google+ for a updates[/URL]
Code:
[url="http://github.com/LiquidSmooth"]LiquidSmooth Github[/URL]
OPL
LiquidSmooth Jewel 3.1 07/25 OPL
NPL
LiquidSmooth Jewel 3.1 07/25 NPL
Please Support Liquid by Donating HERE
INFO
This is a stable beta build for the HTC Evo 4G LTE (Jewel).
Bugs:
Pie needs a reboot to show up
Click to expand...
Click to collapse
HTC Evo 4G LTE specific bugs:
Let me know so i can edit this.
If you encounter any, please be specific in your reporting, so that the issue can be more quickly and easily resolved.
Click to expand...
Click to collapse
Install Instructions:
1. Download ROM
2. Reboot into recovery
3. Please backup your ROM before you begin!
4. You need a full wipe.
5. Flash the ROM
6. Flash 4.4 Gapps
7. Reboot
8. Let it sit a while.
Click to expand...
Click to collapse
Beat me to this one good work sir. You or numel should try resurrection remix...
Looking forward to the new partition build. Will try as soon as you put it up. Thanks!
Sent from my Nexus 5 using XDA Premium 4 mobile app
Got a soccer game in a lil bit bit I will try to get it up at soon I get back
Sent from my EVO LTE using Tapatalk
Op updated
OP UDATED
New Partition Layout Untested
Superwipe!!
Can I use the OSE gapps
Sent from my EVO using Tapatalk
hondafreak513 said:
Can I use the OSE gapps
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
Yep.
Thanks mass, tronit. On top of it as usual. Super happy to see old partition supported .
Sent from my EVO 4G LTE using XDA Premium 4 mobile app
Well install error failed to update binary updater scripts or whatever it is..
Same as sokp ROM is doing..
Sent from my EVO using Tapatalk
First attempt at flashing the NPL results in a fail due to updater binary.
Sent from my Nexus 5 using XDA Premium 4 mobile app
hondafreak513 said:
Well install error failed to update binary updater scripts or whatever it is..
Same as sokp ROM is doing..
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
Agh really I will look into don't think tonite but I will get to it sorry guys
Sent from my EVO LTE using Tapatalk
TroNit said:
Agh really I will look into don't think tonite but I will get to it sorry guys
Sent from my EVO LTE using Tapatalk
Click to expand...
Click to collapse
No problem thanks for bringing more life to our phones..
Sent from my EVO using Tapatalk
@TroNit @numel007
for new format builds
resync device/htc/jewel from cm and pull the new pick
git fetch http://review.cyanogenmod.org/CyanogenMod/android_device_htc_jewel refs/changes/45/59845/6 && git cherry-pick FETCH_HEAD
rebuild and done. Everyone flashing will need the newest recovery from either mdmower or captainthrowback
here: http://forum.xda-developers.com/showthread.php?p=50112370
GoblinZ said:
@TroNit @numel007
for new format builds
resync device/htc/jewel from cm and pull the new pick
git fetch http://review.cyanogenmod.org/CyanogenMod/android_device_htc_jewel refs/changes/45/59845/6 && git cherry-pick FETCH_HEAD
rebuild and done. Everyone flashing will need the newest recovery from either mdmower or captainthrowback
here: http://forum.xda-developers.com/showthread.php?p=50112370
Click to expand...
Click to collapse
Added. Thank you.
Sent from my Nexus 5 using Tapatalk
GoblinZ said:
@TroNit @numel007
for new format builds
resync device/htc/jewel from cm and pull the new pick
git fetch http://review.cyanogenmod.org/CyanogenMod/android_device_htc_jewel refs/changes/45/59845/6 && git cherry-pick FETCH_HEAD
rebuild and done. Everyone flashing will need the newest recovery from either mdmower or captainthrowback
here: http://forum.xda-developers.com/showthread.php?p=50112370
Click to expand...
Click to collapse
Yea in certain point u will need to update Recovery's with the new commits but not to flash this first build. I see the updater is missing stuff so if someone want to swap updaters script and try let me know but it will get fix hopefully.
Edit.
NPL link removed till fix.
Sent from my EVO LTE using Tapatalk
Well its gonna be a bit till I can try to help I tried updating my recovery and now I lost recovery all together now..
Sent from my EVO using Tapatalk
hondafreak513 said:
Well its gonna be a bit till I can try to help I tried updating my recovery and now I lost recovery all together now..
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
It's not hard to reinstall recovery if you know how to use fastboot.
Sent from my Nexus 5 using Tapatalk
numel007 said:
It's not hard to reinstall recovery if you know how to use fastboot.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I finally got it through fastboot, but have a tough time trying to add the new theme capt posted, right now its stuck with venom's theme..
Can someone pass me a recovery log please after the build failed??
Need feedbacks from the old partition as well.
Sent from my EVO LTE using Tapatalk
I'm so sorry about this thread.
Today, I tried to build this rom from source but I faced with a lot of problem because no dev do this rom so I try to it by myself.
Here is there steps I did:
download source code with repo.
- Prepare kernel: I use some guide in AOSP to build this kernel.
- Repair software binaries: Im just download it from Xperia dev.
the first big thing I got is when I use command breafast to build, I didn't not find anything about my device althought I create some folder and place the material on this as same as the guide in AOSP.
So can someone help me rewrite these code to make it work ?
max26292 said:
I'm so sorry about this thread.
Today, I tried to build this rom from source but I faced with a lot of problem because no dev do this rom so I try to it by myself.
Here is there steps I did:
download source code with repo.
- Prepare kernel: I use some guide in AOSP to build this kernel.
- Repair software binaries: Im just download it from Xperia dev.
the first big thing I got is when I use command breafast to build, I didn't not find anything about my device althought I create some folder and place the material on this as same as the guide in AOSP.
So can someone help me rewrite these code to make it work ?
Click to expand...
Click to collapse
You can use OmniROM as a source. Re-writing the sources to compile should not be a big thing. Can you share your sources?
eagleeyetom said:
You can use OmniROM as a source. Re-writing the sources to compile should not be a big thing. Can you share your sources?
Click to expand...
Click to collapse
first i Follow this guide: https://wiki.lineageos.org/devices/nicki/build
and change these thing on this step with something under this line: Prepare the device-specific code
after that I use this guide to build suzu kernel: https://developer.sonymobile.com/op.../#how-to-automatically-build-the-linux-kernel
And I download binaries from source: https://developer.sonymobile.com/op.../#how-to-automatically-build-the-linux-kernel
and I store these thing on google cloud engine, so how to share it to you?
max26292 said:
first i Follow this guide: https://wiki.lineageos.org/devices/nicki/build
and change these thing on this step with something under this line: Prepare the device-specific code
after that I use this guide to build suzu kernel: https://developer.sonymobile.com/op.../#how-to-automatically-build-the-linux-kernel
And I download binaries from source: https://developer.sonymobile.com/op.../#how-to-automatically-build-the-linux-kernel
and I store these thing on google cloud engine, so how to share it to you?
Click to expand...
Click to collapse
I recommend Github
eagleeyetom said:
I recommend Github
Click to expand...
Click to collapse
I read that limit bandwidth is 1gb per month and storage is 5gb, isn't it?
I didn't rewrite any code, just build everything from the source
https://github.com/max26292/lineageos_suzu
Hold on. I'm planning to start working on a custom ROM after fixing the encryption in TWRP. Github has almost unlimited storage, so you shouldn't be worried. You need to fork the OmniROM tree for suzu and loire-common and adapt it to work with LOS.
eagleeyetom said:
Hold on. I'm planning to start working on a custom ROM after fixing the encryption in TWRP. Github has almost unlimited storage, so you shouldn't be worried. You need to fork the OmniROM tree for suzu and loire-common and adapt it to work with LOS.
Click to expand...
Click to collapse
ok i will try :3 I read some guide but It didn't give me enough knowledge to build
eagleeyetom said:
Hold on. I'm planning to start working on a custom ROM after fixing the encryption in TWRP. Github has almost unlimited storage, so you shouldn't be worried. You need to fork the OmniROM tree for suzu and loire-common and adapt it to work with LOS.
Click to expand...
Click to collapse
I'm waiting for great News about your custom rom Projekt, Are there progresses?
rec0re said:
I'm waiting for great News about your custom rom Projekt, Are there progresses?
Click to expand...
Click to collapse
Not yet. I need to sort out my health issues first.
Have you any news about LineageOS for Xperia X?
At this time, no develop build this rom for our device
Maybe had better to wait Android O with vendor layer and LOS 15, will be much easier to update.
@eagleeyetom
As I wanted to get into android rom development/building, I started today syncing the LOS source an forking the omnirom device tree for suzu and loire-common and adapted already some stuff a little bit.
But you probably know more than me about this, so when forking the device tree, loire-commen, etc... for suzu from omnirom, there are these omni.dependencies files, I somehow don't have a plan what to do with those.
Do they need some adapting too or something else?
I would be very grateful if you could point me into the right direction what do with them.
Greetings.
SahilCrazy said:
@eagleeyetom
As I wanted to get into android rom development/building, I started today syncing the LOS source an forking the omnirom device tree for suzu and loire-common and adapted already some stuff a little bit.
But you probably know more than me about this, so when forking the device tree, loire-commen, etc... for suzu from omnirom, there are these omni.dependencies files, I somehow don't have a plan what to do with those.
Do they need some adapting too or something else?
I would be very grateful if you could point me into the right direction what do with them.
Greetings.
Click to expand...
Click to collapse
You need to clone all the repos mentioned in that file. If you are porting LOS, just leave it blank until it gets official.
eagleeyetom said:
You need to clone all the repos mentioned in that file. If you are porting LOS, just leave it blank until it gets official.
Click to expand...
Click to collapse
Yeah I cloned them all and created a manifest where I included them all to sync them all with "repo sync" and to place them in the correct folders etc.
But it looks like theres something wrong with the sepolicy in loire-common:
Code:
device/sony/loire-common/sepolicy/device.te:4:ERROR 'duplicate declaration of type/attribute' at token ';' on line 39737:
type trim_area_partition_device, dev_type;
type persist_block_device, dev_type;
checkpolicy: error(s) encountered while parsing configuration
/root/android/system/out/host/linux-x86/bin/checkpolicy: loading policy configuration from /root/android/system/out/target/product/suzu/obj/ETC/sepolicy_intermediates/policy.conf
[ 28% 16734/57899] Import includes file: /root/android/system/out/target/product/suzu/obj/EXECUTABLES/init_intermediates/import_includes
ninja: build stopped: subcommand failed.
make: *** [ninja_wrapper] Error 1
This happens later also with init.te and tad.te, not only device.te. I tried commenting those lines out but this resulted in an error saying that theres no type declaration.
SahilCrazy said:
Yeah I cloned them all and created a manifest where I included them all to sync them all with "repo sync" and to place them in the correct folders etc.
But it looks like theres something wrong with the sepolicy in loire-common:
Code:
device/sony/loire-common/sepolicy/device.te:4:ERROR 'duplicate declaration of type/attribute' at token ';' on line 39737:
type trim_area_partition_device, dev_type;
type persist_block_device, dev_type;
checkpolicy: error(s) encountered while parsing configuration
/root/android/system/out/host/linux-x86/bin/checkpolicy: loading policy configuration from /root/android/system/out/target/product/suzu/obj/ETC/sepolicy_intermediates/policy.conf
[ 28% 16734/57899] Import includes file: /root/android/system/out/target/product/suzu/obj/EXECUTABLES/init_intermediates/import_includes
ninja: build stopped: subcommand failed.
make: *** [ninja_wrapper] Error 1
This happens later also with init.te and tad.te, not only device.te. I tried commenting those lines out but this resulted in an error saying that theres no type declaration.
Click to expand...
Click to collapse
You can try to build permissive first and try to fix sepolicy later.
eagleeyetom said:
Yeah I cloned them all and created a manifest where I included them all to sync them all with "repo sync" and to place them in the correct folders etc.
But it looks like theres something wrong with the sepolicy in loire-common:
You can try to build permissive first and try to fix sepolicy later.
Click to expand...
Click to collapse
Okey, how do you build permissive? There needs to be something done in the kernel/.../security/selinux/makefile or am I wrong?
SahilCrazy said:
Okey, how do you build permissive? There needs to be something done in the kernel/.../security/selinux/makefile or am I wrong?
Click to expand...
Click to collapse
Take this line as a reference: https://github.com/OrdenKrieger/android_device_zuk_ham/blob/cm-14.1/BoardConfig.mk#L51
eagleeyetom said:
Take this line as a reference: https://github.com/OrdenKrieger/android_device_zuk_ham/blob/cm-14.1/BoardConfig.mk#L51
Click to expand...
Click to collapse
So here's the first boot:
{
"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"
}
I switched the sources, I used now the repos from sonyxperiadev instead of omnirom as I kept getting the sepolicy errors even when I tried building permissive.
There are a few things that still need work, like the sim is not recognized etc.
Will release it here on xda when most of stuff is working fine.
Thanks for your great help!:good:
SahilCrazy said:
So here's the first boot:
I switched the sources, I used now the repos from sonyxperiadev instead of omnirom as I kept getting the sepolicy errors even when I tried building permissive.
There are a few things that still need work, like the sim is not recognized etc.
Will release it here on xda when most of stuff is working fine.
Thanks for your great help!:good:
Click to expand...
Click to collapse
Congratulations! I hope that you will make it stable soon
{
"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 <std_disclaimer.h>
/*
* Your warranty is 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.
*/
Now that I'm done saving my butt, let's proceed
Potato Open Sauce Project is a butter smooth Android aftermarket firmware.
We handpicked the best features around and are adding our own sauce to it.
Get ready to taste the unique features it brings with itself.
We aim to deliver an experience with original ideas and features along with the useful things
the community is accustomed to.
Team Potato
@Agent_fabulous
@ZerNico
@raj_jdja
@ShreyanshLodha
@ATechnoHazard
@HrX
Design:
@McAwesomePL
Valvze
Joshua Baldassarre
Got an issue or suggestion? Reach us at
Telegram: https://telegram.me/SaucyPotatoesOfficial
Twitter: https://twitter.com/PotatoAndroid
- Custom RGB/HSL/HSV accent picker for dark/light themes
- Custom volume panels
- Three mode Notch Handler (Notch-City)
- Icon shapes and icon pack support
- Lockscreen media art and media art blur level
- Permission hub
- Signature spoofing
- QS panel tweaks
- Various custom QS tiles
- Custom clocks
- Brightness slider tweaks
- Doubletap/longpress power to toggle Flashlight
- Double tap to sleep on lockscreen
- Per app network isolation option
- Google feed integration in launcher
- Other miscellaneous tweaks
POSP: PotatoProject
POSP Device Sources: PotatoDevices
POSP Code Review: Gerrit Code Review
xiaomi-sdm845 common kernel: PotatoDevices/kernel_xiaomi_sdm845
Clean Install
- Backup all your data (Important)
- Wipe /system, /data and cache.
- Flash the ROM + NikGApps (Download link below)
- Reboot
Updates
- Flash ROM
- Reboot!
ROM: https://sourceforge.net/projects/posp/files/beryllium/dumaloo
NikGApps: NikGApps
Credits
- Google for AOSP
- Team Potato
- LineageOS
- ArrowOS
- OmniROM
- AOSiP
- And everyone else who helped out!
Give some screenshots
Have anyone tried? Any ir face unlock and The good stuff?
JD. A said:
Have anyone tried? Any ir face unlock and The good stuff?
Click to expand...
Click to collapse
Running POSP now. Smooth ui, no face unlock at all and few customization options. The ones that are there are very polished. Will keep running it and hoping for more updates to come. Also running f2fs on data and no problems there.
@Agent_fabolous,
Its trying to start service 'vendor.vr-1-0' and then crashing. See attached kernel logs
Hello, can u add call recording in aosp vanilla dialer?
@Agent_fabulous Could you upload a new build please?
vivekpf said:
Hello, can u add call recording in aosp vanilla dialer?
Click to expand...
Click to collapse
On it!
MusterMaxMueller said:
@Agent_fabulous Could you upload a new build please?
Click to expand...
Click to collapse
Just pushed one, changelog to follow shortly
MusterMaxMueller said:
@Agent_fabolous,
Its trying to start service 'vendor.vr-1-0' and then crashing. See attached kernel logs
Click to expand...
Click to collapse
Yeah, just noticed; will fix soon. We are now following a weekly release cycle, so you should see a lot more Quality of Life, feature and fixup changes being merged.
Agent_fabulous said:
On it!
Just pushed one, changelog to follow shortly
Yeah, just noticed; will fix soon. We are now following a weekly release cycle, so you should see a lot more Quality of Life, feature and fixup changes being merged.
Click to expand...
Click to collapse
Hi, tried to build POSP from source but wont Boot, stuck at POCO logo. Also manually checked Out vendor_xiaomi_sdm845_common. Do current sources produce a bootable build? Is there something else required?
Waiting new buid. I hope soon
MusterMaxMueller said:
Hi, tried to build POSP from source but wont Boot, stuck at POCO logo. Also manually checked Out vendor_xiaomi_sdm845_common. Do current sources produce a bootable build? Is there something else required?
Click to expand...
Click to collapse
Builds are reproduceable, all public builds are compiled directly from our sources. You will see a failure on Jenkins if something is broken.
Bash:
repo init -u https://github.com/PotatoProject/manifest -b dumaloo-release
repo sync
source build/envsetup
brunch beryllium
adb reboot sideload
adb sideload $OUT/potato_beryllium-11*.zip
adb reboot
neodante said:
Waiting new buid. I hope soon
Click to expand...
Click to collapse
New build is out
Grab it here! I will update the changelog shortly.
Agent_fabulous said:
Builds are reproduceable, all public builds are compiled directly from our sources. You will see a failure on Jenkins if something is broken.
Bash:
repo init -u https://github.com/PotatoProject/manifest -b dumaloo-release
repo sync
source build/envsetup
brunch beryllium
adb reboot sideload
adb sideload $OUT/potato_beryllium-11*.zip
adb reboot
New build is out
Grab it here! I will update the changelog shortly.
Click to expand...
Click to collapse
Please mention the change logs.
Agent_fabulous said:
Builds are reproduceable, all public builds are compiled directly from our sources. You will see a failure on Jenkins if something is broken.
Bash:
repo init -u https://github.com/PotatoProject/manifest -b dumaloo-release
repo sync
source build/envsetup
brunch beryllium
adb reboot sideload
adb sideload $OUT/potato_beryllium-11*.zip
adb reboot
New build is out
Grab it here! I will update the changelog shortly.
Click to expand...
Click to collapse
i had to remove [email protected] from vendor_xiaomi_sdm845-common/sdm845-common-vendor.mk otherwise it wouldnt build. any suggestions why this might be the case?
greatcoder said:
Please mention the change logs.
Click to expand...
Click to collapse
look at github
Agent_fabulous said:
Builds are reproduceable, all public builds are compiled directly from our sources. You will see a failure on Jenkins if something is broken.
Bash:
repo init -u https://github.com/PotatoProject/manifest -b dumaloo-release
repo sync
source build/envsetup
brunch beryllium
adb reboot sideload
adb sideload $OUT/potato_beryllium-11*.zip
adb reboot
New build is out
Grab it here! I will update the changelog shortly.
Click to expand...
Click to collapse
Where is the link for new build ?
Agent_fabulous said:
On it!
Just pushed one, changelog to follow shortly
Yeah, just noticed; will fix soon. We are now following a weekly release cycle, so you should see a lot more Quality of Life, feature and fixup changes being merged.
Click to expand...
Click to collapse
still not fixed
thank you for this awesome rom!
neodante said:
Where is the link for new build ?
Click to expand...
Click to collapse
PotatoHub
POSP Website
potatoproject.co
@Agent_fabulous could you set the default Bluetooth audio sample rate for aptx to 44.1kHz? Sounds better than 48kHz. Thanks
@Agent_fabulous could you push the device tree changes to github/make them public please?