CyanogenMod 11 (Android 4.4.2) For Xperia E Project Home/Status Page
{
"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"
}
Working:
Display
Audio
Bluetooth
WiFi
RIL
Video Playback (SW/HW)
Mobile Data (3G)
LED's
Magnetometer (Screen Rotate)
ART
Vibrator
Battery/Charging
Sound Recording
Not Working:
Camera
Video Recording
FM Radio
All Download Links at http://p.pw/bagB9E
Source: On My Github
Local Manifest: Click Here
Thanks To Everyone in the TamsuiCM11 Team Who Made This Possible!
@lozohcum
Since I'm the only developer working on CM11 For Xperia E (Where is @hsr0 ) I'm looking at where we can start at bug fixing. What information do I need to give you to diagnose the problems?.... I guess logcat etc.
This is what I did:
Compiled with using the lights.c from CM Repo
Compiled with all things under Audio commented due to AudioHardware.cpp Errors.
Compiled Using Default Toolchain.
SELinux is Still Disabled Although I have added the correct lines needed.
Where to go from now?
Firstly, @UltraGamerHD, can you please fix the thread title? It's says "4.2.2", where it should say "4.4.2". Awesome, thanks!
Secondly, whenever I try to sync, the local manifest causes problems. lozohcum said to download manually, but I'm not sure how to do that. I'm also doing CM11 - for now.
NSDCars5 said:
Firstly, @UltraGamerHD, can you please fix the thread title? It's says "4.2.2", where it should say "4.4.2". Awesome, thanks!
Secondly, whenever I try to sync, the local manifest causes problems. lozohcum said to download manually, but I'm not sure how to do that. I'm also doing CM11 - for now.
Click to expand...
Click to collapse
Get a Fresh Install of Ubuntu 13.10 and Follow this guide here: http://forum.xda-developers.com/showthread.php?t=2464683
Do Every Command EXCEPT FROM THE LAST 3
Now Type this in Terminal:
Code:
mkdir ~/cm11
Code:
cd ~/cm11
Code:
git config --global user.name YOUR NAME
Code:
git config --global user.email YOUR EMAIL
Code:
repo init -u git://github.com/CyanogenMod/android.git -b stable/cm-11.0
Code:
repo sync
---------------------------------------------------------------
Now lets setup the TamsuiCM11 Repo Manifest
Type this in Terminal:
Code:
. build/envsetup.sh
Then go into cm11 folder using the file manager and press Ctrl + H, you will now find a folder called .repo. Go inside the .repo folder.
Inside the folder create a folder called
Code:
local_manifests
Exit the folder back to the cm11 folder and press Ctrl + H again.
Now go back to Termial and Type:
Code:
gedit ~/cm11/.repo/local_manifests/local_manifest.xml
Copy this into the document:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- Dependancies -->
<project path="device/sony/tamsui-common" name="TamsuiCM11/android_device_sony_tamsui-common" revision="cm-11.0" />
<project path="kernel/sony/msm7x27a" name="TamsuiCM11/android_kernel_sony_msm7x27a" revision="master" />
<project path="device/sony/qcom-common" name="CyanogenMod/android_device_sony_qcom-common" revision="cm-11.0"/>
<project path="device/sony/common" name="CyanogenMod/android_device_sony_common" revision="cm-11.0"/>
<project path="kernel/sony/nanhu_ds" name="TamsuiCM11/android_kernel_sony_msm7x27a-nanhu" revision="cm-11.0" />
<!-- Devices -->
<project path="device/sony/tapioca_ss" name="TamsuiCM11/android_device_sony_tapioca_ss" revision="cm-11.0"/>
<project path="device/sony/jlo" name="TamsuiCM11/android_device_sony_jlo" revision="cm-11.0" />
<project path="device/sony/mesona" name="TamsuiCM11/android_device_sony_mesona" revision="cm-11.0" />
<project path="device/sony/nanhu_ds" name="TamsuiCM11/android_device_sony_nanhu_ds" revision="cm-11.0" />
<project path="hardware/atheros/wlan" name="CyanogenMod/android_hardware_atheros_wlan" revision="jellybean" />
<!-- Proprietary files -->
<project path="vendor/sony" name="TamsuiCM11/proprietary_vendor_sony" revision="cm-11.0" />
<!-- Drivers -->
<project path="hardware/qcom/display-legacy" name="TamsuiCM11/android_hardware_qcom_display-legacy" revision="cm-11-jlo" />
<project path="hardware/qcom/audio-legacy" name="TamsuiCM11/android_hardware_qcom_audio-legacy" revision="cm-11.0" />
<project path="hardware/qcom/media-legacy" name="TamsuiCM11/android_hardware_qcom_media-legacy" revision="cm-11.0" />
</manifest>
Save and exit.
Then Type
Code:
repo sync
Your Done @NSDCars5
@NSDCars5 go to github site of repo you want to use, let's say it's jlo in my case: https://github.com/TamsuiCM11/android_device_sony_jlo
Select brunch you want to use, and then click Download ZIP button on the right side.
Then upack that folder, rename to jlo and move to device/sony.
Same with other repos.
Btw after I redownlaod everything I don't have any problems with syncing.
You can work on Builduntu.
joebonrichie is working on CM11 too.
These days I can't give my time to CM11 because I'm doing driving license and have some school stuff unfinished. I also have matura exam in May.
At the moment I'm rebuilding rom due to problems with Audio HAL. @UltraGamerHD you have to find the most similar device to XE and see how other devs worked on it. Learn by observation, reading and trying, there os no single way to just fix errors. Many times reading logcat gives you the most important informations how to solve the problem, just think a lot an try to remember which file refers to what in logcat.
I'm not dev who can code, understand everything and can write app from scratch. But I've learned a lot first by porting roms and then by
reading the code for tens of hours.
@lozohcum, @UltraGamerHD: Thanks a lot! I'll try these soon as I get home. Buildbuntu in particular looks pretty awesome.
For some related development, I say we should look at the HTC Explorer and the LG Optimus L7; both are pretty similar to the E, hardware-wise (well, we also have the Galaxy Ace Plus, but I think lozohcum said we shouldn't look at Samsung for development).
lozohcum said:
@NSDCars5 go to github site of repo you want to use, let's say it's jlo in my case: https://github.com/TamsuiCM11/android_device_sony_jlo
Select brunch you want to use, and then click Download ZIP button on the right side.
Then upack that folder, rename to jlo and move to device/sony.
Same with other repos.
Btw after I redownlaod everything I don't have any problems with syncing.
You can work on Builduntu.
joebonrichie is working on CM11 too.
These days I can't give my time to CM11 because I'm doing driving license and have some school stuff unfinished. I also have matura exam in May.
At the moment I'm rebuilding rom due to problems with Audio HAL. @UltraGamerHD you have to find the most similar device to XE and see how other devs worked on it. Learn by observation, reading and trying, there os no single way to just fix errors. Many times reading logcat gives you the most important informations how to solve the problem, just think a lot an try to remember which file refers to what in logcat.
I'm not dev who can code, understand everything and can write app from scratch. But I've learned a lot first by porting roms and then by
reading the code for tens of hours.
Click to expand...
Click to collapse
Thanks for the Advice.
Just be carefull with samsung. Source porting is fine that way.
@UltraGamerHD
I've noticed some differences between FXP CM11 tamsui-common-legacy (jlo/tapioca/mesona) and tamsui-common (nanhu).
in tamsui.mk, tamsui-common-legacy has the following snippet for RIL
Code:
# Radio
PRODUCT_PROPERTY_OVERRIDES += \
[B]ro.telephony.ril_class=SonyQualcommRIL7x27a \[/B]
[B]ro.telephony.ril.v3=skipnullaid \[/B]
rild.libpath=/system/lib/libril-qc-1.so \
rild.libargs=-d/dev/smd0 \
persist.rild.nitz_plmn= \
persist.rild.nitz_long_ons_0= \
persist.rild.nitz_long_ons_1= \
persist.rild.nitz_long_ons_2= \
persist.rild.nitz_long_ons_3= \
persist.rild.nitz_short_ons_0= \
persist.rild.nitz_short_ons_1= \
persist.rild.nitz_short_ons_2= \
persist.rild.nitz_short_ons_3= \
ril.subscription.types=NV,RUIM \
DEVICE_PROVISIONED=1 \
keyguard.no_require_sim=1 \
ro.ril.hsxpa=1 \
ro.ril.gprsclass=10 \
ro.use_data_netmgrd=true \
persist.data_netmgrd_nint=3 \
ro.ril.transmitpower=true
in tamsui.mk, in tamsui-common (nanhu)
Code:
# Radio
PRODUCT_PROPERTY_OVERRIDES += \
[B]ro.telephony.ril_class=SonyQualcommRIL \[/B]
[B]ro.telephony.ril.v3=qcomdsds \[/B]
ro.telephony.call_ring.multiple=false \
rild.libpath=/system/lib/libril-qc-1.so \
rild.libargs=-d/dev/smd0 \
ril.subscription.types=NV,RUIM \
DEVICE_PROVISIONED=1 \
keyguard.no_require_sim=1 \
ro.use_data_netmgrd=true \
ro.ril.transmitpower=true \
persist.data.ds_fmc_app.mode=0 \
persist.ims.regmanager.mode=0
i've bolded the importance differences between the two, as you can see nanhu used a different RIL. If we can find SonyQualcommonRIL.java about somewhere maybe we could fix RIL on nanhu.
So I found this SonyQualcommRIL.java; see if it can be used: https://github.com/OpenSEMC/android...telephony/java/com/android/internal/telephony
NSDCars5 said:
So I found this SonyQualcommRIL.java; see if it can be used: https://github.com/OpenSEMC/android...telephony/java/com/android/internal/telephony
Click to expand...
Click to collapse
@joebonrichie
It's been found
Just few questions.
1) Is it that slow when it was on that first build which you deleted?
2) Xperia E have IRC channel available? I know few devs which can help you out there.
I think the closest device is to our mobile is HTC explorer slight difference in out chipset(ours is faster).
icoolguy1995 said:
Just few questions.
1) Is it that slow when it was on that first build which you deleted?
2) Xperia E have IRC channel available? I know few devs which can help you out there.
I think the closest device is to our mobile is HTC explorer slight difference in out chipset(ours is faster).
Click to expand...
Click to collapse
1) Yes the same thing and this time I build with @hsr0 device tree.
2) Don't Know!
@icoolguy1995
@Aniruddh Chandratre
The ROM is like no other rom, it takes 3 mins to open up the App Drawer and the boot animation is not even smooth at all!
Any help?
Or is the XE CM11 Project Dead.
UltraGamerHD said:
@Aniruddh Chandratre
The ROM is like no other rom, it takes 3 mins to open up the App Drawer and the boot animation is not even smooth at all!
Any help?
Or is the XE CM11 Project Dead.
Click to expand...
Click to collapse
can you provide log/kmesg?
nanhu is slightly different from Tamsuis, more like 2013 Sony devices, but with Tamsui generation hardware. and i think that it was developed by different Sony Devs (you can look on nanhu kernel, way different from Tamsui).
AshRoller said:
can you provide log/kmesg?
nanhu is slightly different from Tamsuis, more like 2013 Sony devices, but with Tamsui generation hardware. and i think that it was developed by different Sony Devs (you can look on nanhu kernel, way different from Tamsui).
Click to expand...
Click to collapse
@AshRoller
@lozohcum
@joebonrichie
kmsg: https://docs.google.com/file/d/0B73-53ZX-WVRTUZYRXMtX3l3cWs/edit
logcat: https://drive.google.com/file/d/0B73-53ZX-WVRYzJTM1Q4Sl84WWc/edit?usp=sharing
@UltraGamerHD Upload it here, maybe? This URL is easier to memorize: https://github.com/TamsuiCM11/Tamsui_logcats-kmsg/tree/nanhu
Till then, I'll have fun looking at the ones you provided.
NSDCars5 said:
@UltraGamerHD Upload it here, maybe? This URL is easier to memorize: https://github.com/TamsuiCM11/Tamsui_logcats-kmsg/tree/nanhu
Till then, I'll have fun looking at the ones you provided.
Click to expand...
Click to collapse
Done.
So UltraGamerHD PMed me a build of CM11, and I liked it, other than the fact it was pretty slow (he says there are a lot of delays and stuff in the logcat; haven't had time to see it myself yet), and that GSM and WiFi didn't work. Bluetooth doesn't either, but that's a minor problem.
It didn't give any FCs or anything. Here are some shots: https://drive.google.com/folderview?id=0BxkRB3c4ACcZcU5SUkxkVWthWWs&usp=sharing
If anybody asks, I did a factory reset, wiped /system, installed CM11 and PA's micro KitKat Gapps, and rebooted. Boot took about long enough for me to have dinner. However, the ROM was actually not that bad; took only about 10-20 seconds to load the app drawer. It was as though I was playing Asphalt 8; slow, but you know it'd work nice if you get past the speed issue.
took only about 10-20 seconds
Click to expand...
Click to collapse
I like the "only" from that sentence
The logcat you posted is like messy. Can you upload also the result of adb logcat *:E ??
Only booting time.
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"
}
This build i compiled myself completely from source!
I used blahbl4hblah guide and edited a few things to build AOKP! found here Thread Link
Here is the step by step how i did it!
How to compile moved to 3rd post.
Special thanks to:
Click to expand...
Click to collapse
Whitehawkx
Roman
Jonathan Grigg
Zaphod-Beeble
ProTekk
Sethyx
vorbeth
blahbl4hblah
CyanogenMod
CHANGE LOG: Build 33
TEAM KANG
bug fixes
- Bluetooth: Fixed memory leak and file handles leak
- Nav bar & tablet status bar FCs fixed
- Fixed some init.d scripts not running due to lack of bash
- Changing brightness by sliding on the top of the statusbar (if enabled) shouldn’t FC anymore
- Fixed Data toggle not updating properly
- Torch should be acting normally again
- ROM Control: Fixed scrolling cache not setting properly
- Weather will refresh whenever SystemUI starts instead of when the phone boots (so if it gets restarted, it should fetch weather again, it didn’t before)
- Lockscrens: Added lockscreen wallpapers to pin & pattern unlock screens
- Settings: fixed link mute states always being checked
supersonic: Updated files (thanks to evervolv), should boot! I’ve also included a “camera hack” so it should work, Video camera will FC, so will panorama mode. It is what it is
new features
- Added another ROM Control shortcut that opens ROM Control
- Added ability to translate weather conditions (only German is translated for now I think)
- Mms: added ability to strip unicode (CM)
- Mms: added emoji icons (CM)
- Mms: added quick emoji button to left of input (option you must enable)
- Added warnings to fast charge (will notify you if it’s enabled on boot)
- Hide navbar feature for tablets
- More music players supported for AVRCP 1.3
CHANGE LOG: Build 34
fixed mobile data toggle not updating for serious
fix navigation buttons for tablets
long press home options added to General Interface for phones that have hardware buttons
fix icon transparency being applied to right-side buttons (BT, etc)
updated NovaLauncher to 1.1.1
Add BT MAP Profile
fix font sizing in statusbar
fixed volume sliders not updating when volumes are linked
many fixes for ColorPicker in ROM Control
gradient showing properly
color picker should fit in all screens now
show color preview before opening dialog (in-line)
fixed sound playing when volume zoom is enabled in camera
last.fm AVRCP crash fixed
contact pictures now displaying properly in notifications when receiving new sms
CHANGELOG: Build Milestone 5
updated to IMM76I
differences between IMM76D and IMM76I are ALL in the Galaxy Nexus kernel
we updated the Galaxy Nexus kernel to Faux’s 16m kernel by default, which incorporates the fixes from IMM76I
fixed long press home on navbar being on by default
fixed volume zoom playing sounds with video camera
made flash-off indicator visible in camera
AVRCP: fixed soft reboots with certain players
fixed brightness slider jumping when toggling auto-brightness
sped up opening of init.d tweaks in RC
added description to LED setting on RC to be clearer on what it does
it only changes the DEFAULT LED color. Apps may override it, and most do.
attempted to fix freezing clock yet again
fixed wifi icon being cut off
fixed color multipliers being doubled
new gamma ranges from -100 to 100 defaulting to 0
your kernel (if it supports gamma tuning) might have a different default, so just keep that in mind (60 was the previous default)
fixed small icons when airplane mode & wifi are enabled
added shortcuts to toggle torch & toggle navbar
that means you can add these to nav bar as regular actions or long press actions, click “Custom app”, scroll down to “System UI”, toggle nav bar & torch should be there.
You can also add these shortcuts to your desktop. They do NOT work correctly from the lockscreen, yet.
Fixed decrease lights in custom backlight settings
a500 renamed to picasso and updated
everything should work now except slow GPS lock times
Notes (read them!):
this change log is differences between build 34. If you’re coming from M4, you’ll need to read all the change logs from the builds between M4 and M5 (THERE ARE A LOT!)
When you flash themes or mods or kernels, keep in mind that they can change almost any aspect of the ROM and introduce bugs and inconsistencies if not properly packaged for AOKP or not properly updated for Milestone 5.
If you experience a bug after flashing a mod/theme/kernel, do a NANDROID (so you can return to it after testing!), re-flash AOKP and wipe, then test to see if the bug still exists. ONLY THEN REPORT IT TO THE BUG TRACKER.
we tried to smash as many bugs as possible, but no product is ever bug free. Feel free to report any bugs you experience to http://rootzwiki.com...97-bug-tracker/
NOT ALL DEVICES ARE MADE EQUALLY! Some device still have KNOWN bugs!
There are many devices which we support that aren’t as bug free as the Galaxy Nexus or other AOSP devices (such as the Nexus S)
That said, we try and incorporate fixes for all devices that we support from many sources (CyanogenMod, evervolv, Code Aurora Forum, other teams and individual contributors). We thank those teams for making their code open source and available for us to use so you can put AOKP on your device
below are the bugs we are aware of for specific devices
p4: Galaxy Tab 10.1” -- no camera, rotating device causes a slight flicker, potential touch screen issues.
supersonic: camera works, panorama mode & video camera does NOT
galaxysmtd: I have read that it’s GPS doesn’t work 100%
inc: I have read that some people experience device instability and reboots. No one on the team has an incredible to test on, so we can’t confirm or deny this exists.
p999: g2x - browser crashes while switching to landscape, video recorder does not work, USB tethering does not work
p990: O2x - gps does not work at all, video recorder does not work, other potential inconsistencies, potential ROM Control FCs if language is set to anything other than english
pyramid: sensation - 480p video recording is broke (720, 1080 work fine), usb tether does not work
tenderloin: no camera
there may be more bugs that are unlisted, feel free to report them to the bug tracker
Check out the ROM source on github http://github.com/AOKP. Open source, in the spirit of community kangage.
Click to expand...
Click to collapse
Also - special thanks to @Vorbeth and intervigilium https://github.com/intervigilium for the work they put in on the pyramid device tree!
Credits to:
Click to expand...
Click to collapse
RMS
sk8rboikelley -webmaster
sbryan12144
tommytomatoe
Support/Download For ROM Here At This Site. Forums Are Open For Reading And Downloading But Must Register To Post: http://www.android-engineering.com/index.php
RMS AOKP SPASH DOWNLOAD
(Rename zip to PG58IMG flash thru hboot)
Rom Add On's
Carbon theme I ported found HERE. Please hit the mans thanks button.
All I did was add a keyboard and remove the framework.res to keep it from bootlooping. ALL CREDIT GOES TO Jairomeo PLEASE VISIT AND HIT HIS THANKS BUTTON AND POSSIBLY A DONATION THANKS!!
...:: Download ::...
Click Me To Download Theme
Boot to recovery and flash.
HOW TO COMPILE AOKP
================================
Required Software to Install:
================================
10.04 UBUNTU 64-bit System
================================
sudo apt-get install git-core gnupg flex bison python rar original-awk gawk p7zip-full gperf libsdl1.2-dev libesd0-dev libwxgtk2.6-dev squashfs-tools build-essential zip curl libncurses5-dev zlib1g-dev pngcrush schedtool
Click to expand...
Click to collapse
================================
For 64-bit System
================================
sudo apt-get install g++-multilib lib32z1-dev ia32-libs lib32ncurses5-dev lib32readline-gplv2-dev gcc-multilib g++-multilib
Click to expand...
Click to collapse
================================
Other Required Software:
================================
sudo apt-get install libc6-dev x11proto-core-dev libx11-dev libgl1-mesa-dev mingw32 tofrodos python-markdown libxml2-utils
Click to expand...
Click to collapse
================================
sudo ln -s /usr/lib/i386-linux-gnu/libX11.so.6 /usr/lib/i386-linux-gnu/libX11.so
Click to expand...
Click to collapse
================================
1a. MUST Install Java 1.6:
================================
sudo add-apt-repository ppa:ferramroberto/java
sudo apt-get update
sudo apt-get install sun-java6-jdk sun-java6-jre sun-java6-plugin
Click to expand...
Click to collapse
================================
1b. *To Check for Correct Java Version*
java -version
================================
**MUST BE THIS:**
java -version
java version "1.6.0_26"
Java(TM) SE Runtime Environment (build 1.6.0_26-b03)
Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02, mixed mode)
Click to expand...
Click to collapse
================================
1c. Need to remove other java version!
================================
gksudo nautilus
Click to expand...
Click to collapse
================================
Once you enter your password, navigate to 'FILE SYSTEM'
Afterwards navigate to /usr/lib/jvm
If you see an open-jdk folder of any kind delete those folders, there should be two folders.
OR
Press Alt+F2 and look for synaptic, then enter your password for root access then in the search bar look for openjdk and check it to be completely removed. Be sure it's ONLY removing openjdk
================================
********************************
Setting Up Android SDK
********************************
2a. Download Android SDK at http://developer.android.com/sdk/index.html
--------------------------------------------------------------------------
2b. Extract it to your home folder [Ex. ~/android/sdk] Make folder in HOME
name it android. Then extract sdk into it and rename sdk linux folder to sdk!
--------------------------------------------------------------------------
2c. Add Android SDK Path
===============================
gedit ~/.bashrc
Enter the Following:
===============================
#Android PATH
export PATH=$PATH:~/android/sdk
export PATH=$PATH:~/android/sdk/platform-tools
export PATH=$PATH:~/android/sdk/tools
Click to expand...
Click to collapse
-------------------------------------------------------------------------
2d. Add Extra Path For Device:
===============================
sudo gedit /etc/udev/rules.d/51-android.rules
Enter this in it:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
Click to expand...
Click to collapse
===============================
After this, close it and then:
sudo chmod +x /etc/udev/rules.d/51-android.rules
Click to expand...
Click to collapse
===============================
2e. *Install Certain Android SDK Tools*
Then Type:android in terminal!
Click to expand...
Click to collapse
Check Android SDK Tools and Android SDK platform-tools
Install them
===============================
3a. Setting Up the .bashrc file
gedit ~/.bashrc
Enter the Following:
#Java PATH
export JAVA_HOME=/usr/lib/jvm/java-6-sun-1.6.0.26
export PATH=$PATH:$JAVA_HOME/bin
Click to expand...
Click to collapse
===============================
3b. After your done setting this up, close .bashrc file.
===============================
4a. Setup Workplace
mkdir -p ~/bin
mkdir -p ~/android/system
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod a+x ~/bin/repo (Reboot your computer after this)
Click to expand...
Click to collapse
=============================
4b. Add Repo Path
gedit ~/.bashrc
Then add this: export PATH=$PATH:~/bin
Click to expand...
Click to collapse
=============================
4c. Setup Necessary Source!!!
cd ~/android/system/
repo init -u git://github.com/AOKP/platform_manifest.git -b ics
repo sync -j14
Click to expand...
Click to collapse
=============================
=============================
**Then to build:**
. build/envsetup.sh
lunch aokp_pyramid-userdebug
mka bacon
Click to expand...
Click to collapse
**********************************
When build is finished go into home/android/system/out/target/product/pyramid to find yur unofficial build!
good night!
Lookin great Tory!
Sent from my HTC Sensation 4G XE with Beats Audio using XDA
toryheal said:
good night!
Click to expand...
Click to collapse
Kind of a redundant rom, isn't it? You should mention what makes your Guide/ROM different than others.
Thanks for using my guide
Honestly, the ONLY thing you have to change from my guide is the link for the repo init part and the rest is the same
blahbl4hblah said:
Thanks for using my guide
Honestly, the ONLY thing you have to change from my guide is the link for the repo init part and the rest is the same
Click to expand...
Click to collapse
Credit given in OP thanks.
ThatsABigOne said:
Kind of a redundant rom, isn't it? You should mention what makes your Guide/ROM different than others.
Click to expand...
Click to collapse
Variety man you don't have to flash.
toryheal said:
Credit given in OP thanks.
Click to expand...
Click to collapse
Oh no, wasn't pointing to that but thanks
I was originally going to just put the repo init for aokp in my guide.
Maybe just keep this a rom thread, no disrespect at all
blahbl4hblah said:
Oh no, wasn't pointing to that but thanks
I was originally going to just put the repo init for aokp in my guide.
Maybe just keep this a rom thread, no disrespect at all
Click to expand...
Click to collapse
Oh broskii none taken. My bad if I came across like that. Cheers mate.
So quick question for OP or Blah, are proprietary driver files/blobs for sensation already included in the associated git trees? I was trying to figure out if I had to provide those from somewhere. Not clear to me where it is specified that the build is for sensation. Thanks for the help!
Update : Ok never mind I see the pyramid parameter at the end. I was thinking I had to specify a configuration file before compiling. Gonna give it a try.
ThatsABigOne said:
Kind of a redundant rom, isn't it? You should mention what makes your Guide/ROM different than others.
Click to expand...
Click to collapse
From the design itself it looks very cool and i´m really looking forward to your Rom how it develops in time, but for now, as "ThatsABigOne" said, you should mention is categories want works and what kinda bugs your rom has.
So , good luck on your Rom, i´ll keep it in mind =)
alikebab said:
From the design itself it looks very cool and i´m really looking forward to your Rom how it develops in time, but for now, as "ThatsABigOne" said, you should mention is categories want works and what kinda bugs your rom has.
So , good luck on your Rom, i´ll keep it in mind =)
Click to expand...
Click to collapse
What works in OpenSensation is what works in this
toryheal said:
Oh broskii none taken. My bad if I came across like that. Cheers mate.
Click to expand...
Click to collapse
None taken dude, it's all good
I just don't want your first post to be too long, people will get lazy
blahbl4hblah said:
None taken dude, it's all good
I just don't want your first post to be too long, people will get lazy
Click to expand...
Click to collapse
Right on Broskii G'Nite.
Tory, is this comes with stock kernel or faux 005?
Sent from my HTC Sensation using XDA
jay661972 said:
Tory, is this comes with stock kernel or faux 005?
Sent from my HTC Sensation using XDA
Click to expand...
Click to collapse
Stock is faux atm
Actually I'm not sure since I haven't looked at aokp's pyramid device tree
If it's the same kernel as vorbeth's then it's faux's
How is the ROM anyone tried it out
Sent from my Xoom tablet using Tapatalk
blahbl4hblah said:
Stock is faux atm
Actually I'm not sure since I haven't looked at aokp's pyramid device tree
If it's the same kernel as vorbeth's then it's faux's
Click to expand...
Click to collapse
Last I checked, kernel is faux's.
See here: AOKP Pyramid Kernel Update
Thomas.Raines presents
The Lightning Zap! kernel for the Skyrocket
ATTN:
I thomas.raines, nor my affiliates claim responsibility for anything you do to damage, destroy, brick, explode, or otherwise screw up your device.
{
"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 revamped the Lightning Zap! kernel across the board. Since I have so many of them I was loosing where I was on each one. So I have now broken it down into 3 phases:
Phase 1: Introduction of LZ kernel to device
Phase 2: Fine tuning of tweaks, values, etc
Phase 3: Implementation of OC/UV
Phase 4: Continue updating and adjusting as necessary
From now on I will name the .zip accordingly as well:
Sky_p2.1
On a good note, I think this latest update will finalize phase 2 and now I can work on OC/UV...
Features:
Improved performance
Improved battery life
Improved network speeds
Improved boot times
Smoother scrolling
Better responsiveness
Cleaner file systems
Governor tweaks for amazing speed and performance without sacrificing battery life
Improved Memory and Ram tweaks
Improved Internet speed
Amazing kernel tweaks, build.prop mods, init.d scripts and more!
Instructions:
Make a backup
Download LightningZapv1Sky.zip to PC
Transfer LightningZapv1Sky.zip to your sdcard
Or just download it straight to your phone
Reboot to recovery
Flash
Phone will automatically reboot after install**
Wait 10 minutes
Enjoy the Lightning Zap!
ATTN!
If you are currently on any version of Lightning Zap! kernel, you must either replace your build.prop from your ROM or re-flash your current ROM. Or you can open your build.prop with a text editor and delete all lines below the Lightning Zap Tweaks entry.
This kernel was tested on ParanoidAndroid. This kernel and tweaks will work with any version of CM10 post 14OCT.
**First boot, especially after a fresh install of your ROM (wipe system cache etc, flash ROM gapps Lightning Zap) will take a while. It will seem to hang between a blank screen (which use to be the 2nd boot splash) and the boot animation. There is no need to panic. Everything is fine. It is the vacuum script trying to clean databases that have yet to be created. After first boot, your phone will boot as normal (a little faster actually)...
After first boot, ensure your I/O scheduler is set to cfq and your governor is set to ondemand to gain the maximum benefits of Lightning Zap!
See 3rd post for further instructions on improving and customizing your Lighting Zap! experience.
Source Code:
msm8660-common_lz_kernel
vendor_lz-kernel (LZ vendor files for ROM compiling)
LZ Flashing Packages (For those of you just compiling the kernel)
Includes flashing script, binaries, etc for the Blaze, Nitro and Skyrocket
Special thanks to:
gs2usr for the link to source code...
xan for Voltage Control app
Download links and changelog
Downloads and changelog
Skyrocket_p4.4-5.zip
Upstream maintenance
Anybody good with making a custom recovery and want to help out with the dual boot, hit me up...
Skyrocket_p4.4-4A.1.zip
Fixed intermittent boot loop issue
Dual boot has be put on hold for now...
Skyrocket_p4.4-A
Removed topology and mpdecision in 4.4-4, but found all the gov's work best with mpdecision so I added it back.
Adjusted CONFIG_NR_CPUS (number of cpu's) to cm default 999999 which causes the use of a CPU mask array. Small performance hit initially, but an overall vast improvement especially when multi-tasking.
Skyrocket_p4.4-3.zip
Merged from upstream
Added missing msm_mpdecsion blobs
All governors and schedulers seem completely stable now (Keep testing please)
Added True CD-ROM emulation interface (Not fully working on my computer. Need testers to verify with windows and linux) here is how to use it! (Special thanks goes to DooMLoRD and his doom kernel for the Xperia Z)
init.d scripts updated with new mount params
Enjoy!
Skyrocket_p4.4-2.zip
Raised vm_max_readahed to 4096.
Lowered default max cpu freq to 1512.
Changed min cpu freq to 384 to fix Lionheart and Gallimaufry instability.
Skyrocket_p4.4-1.zip
Fixed ability to change cpu frequency. Your changes now stick after closing app.
Used userdebug lunch option. Now if you have red border on screen, it's more than likely in the ROM. Talk to your ROM dev.
Possible fix for loss of su/root. (Let me know if you still loose it after flashing. I didn't have any issues this time.
Skyrocket_p4.4.zip
Updated to 4.4 for cm-11.0. This means this version is for cm-11.0/android 4.4
CPU frequency settings don't stick after closing the VC app
Lionheart governor acts up a bit and might cause reboots if voltage is too low
Lowering cpu frequency below 384 may cause instability
Still testing. If you find any bugs, let me know and please add a logcat
Archived changelog
Enjoy the Zap!
Voltage tables:
Voltage tables:
Voltage minimum
Was 1000mV
Now 700mV
Voltage max
Was 1250
Now 1350
With a 25mV step between frequencies; however, 192mV-423mV are all three 700mV
The governor tweak is set for a fairly balance of performance and battery life. If you find yourself needing battery life over performance, you can make some minor changes. Here's how:
1 Download Script Manager from the market (it's free)
2 Open Script Manager and navigate to /system/etc/init.d
3 Press menu/more/advanced options and select mount as RW
4 Select 01governor and select "edit" at the top (this will open the file in atext editor)
5 Uncomment (remove # in the particular line) and change:
Code:
echo "45" > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold;
To:
Code:
echo "[COLOR=red]70[/COLOR]" > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold;
6 Select menu/save
7 Press the skull and cross bones icon at the top (this will allow Super User)
8 Press run, close app and enjoy
This will result is slightly slower performance but higher battery life.
If you want even better battery life:
1 Following steps 1-4
2 Add a # at the begining of lines 11 to 19
3 Scroll to "pwoersaver" section
4 Remove the # at the begining of lines 28, 30-38 and 43
Code:
#AWAKE_GOVERNOR="ondemand"
#SLEEP_GOVERNOR="ondemand"
# echo "70" > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold;
etc
Code:
AWAKE_GOVERNOR="powersaver"
#SLEEP_GOVERNOR="powersaver"
echo "20000" > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate;
5 Follow steps 6-8 (no need to select super user icon if you already did)
This will result in lower performance, but ultimate battery life
When running in a higher performance mode (especially for gaming) you can disable powersave_bias by changing the 1 to a 0 like this:
Code:
echo "1" > /sys/devices/system/cpu/cpufreq/ondemand/powersave_bias;
echo "[COLOR=red]0[/COLOR]" > /sys/devices/system/cpu/cpufreq/ondemand/powersave_bias;
Powersave_bias only allows the CPU to peak for small increments at a time, and not allow the CPU to remain peaked even when the system calls for it. In gaming, that could result in choppy, laggy perofrmance and slow FPS..
Although it says not to in the script, you can change the sampling rate as well. Do not go below 50000. I left it at 57500 as I found this seems good setting for smooth scrolling and performance.
Code:
echo "[COLOR=Red]57500[/COLOR]" > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate;
Always leave SLEEP_GOVERNOR="powersave" uncommented (no #) and do not uncomment any other SLEEP_GOVERNOR as this will keep ultimate battery save while screen is off.
Only change values in increments of 5 for the up_threshold.
I am not resposible if you do something wrong. Make a back up just in case.
Source code tips
just add this to your local_manifest.xml:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote fetch="https://github.com" name="LZkernel" />
<project name="TeamFahQ/msm8660-common_lz_kernel" path="kernel/samsung/msm8660-common" remote="LZkernel" revision="jellybean" />
<project name="TeamFahQ/vendor_lz-kernel" path="vendor/lz-kernel" remote="LZkernel" revision="master" />
<project name="TeamFahQ/android_device_samsung_msm8660-common" path="device/samsung/msm8660-common" remote="github" revision="jellybean" />
<project name="TeamFahQ/android_device_samsung_skyrocket" path="device/samsung/skyrocket" remote="github" revision="jellybean" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_device_samsung_celox-common" path="device/samsung/celox-common" remote="github" revision="jellybean" />
</manifest>
You MUST use my repo for the devices (as noted above) in order for LZ to build correctly. You will also need to manually copy the /scripts and modules to your directory where you zip things up. /system/etc/lzbp.sh is gone so make sure you remove the perms from your flashing script (Working on fixing this now)
Or (in terminal):
Code:
curl -L -o .repo/local_manifest.xml -O -L https://raw.github.com/TeamFahQ/Paranoid_manifest/master/local_manifest.xml
And remove the devices that you do not wish to use. Then repo sync. If you are using this as a basis for another device, make sure you check out the commits.
thomas.raines said:
Sorry guys... My lack of patience for trolls got the best of me for the moment...
Anyhow, let's get on with the good stuff. The OP is complete, the CWM flashable zip is uploaded, and the link is validated and ready for you guys. Please allow at least 24 hours and 1 recharge cycle to pass before posting results and issues. If you do encounter an issue, please provide logs.
Click to expand...
Click to collapse
Since that's over I'm downloading now can't wait to see what happens
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
---------- Post added at 01:27 AM ---------- Previous post was at 01:05 AM ----------
i can confirm that this works on the latest slim bean 2.8 ill give it a full run to see how it feels and if it saves battery and performance
Awesome! digging the influx of kernels lately, will give this one a shot :good: :good:
Gonna give this a whirl on xperiance aokp r3
Sent from my SGH-I727 using Tapatalk 2
forgive me if i miss details . i try to look which rom this support . iam running liquid RC 5 . the other two kernel only support build after 10-14th.
what about this one ? the same ?
christianxin said:
forgive me if i miss details . i try to look which rom this support . iam running liquid RC 5 . the other two kernel only support build after 10-14th.
what about this one ? the same ?
Click to expand...
Click to collapse
I'm honestly not real sure man. All I can say is flash it and see... I can tell you this is a CM9/10 kernel...
Whoa another kernel XD this ones sounds cool Ima try it for the hercules
Sent from my Paranoid SGH-T989 with KKO
Good to see you got it done. Nice job!
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Working well on orothus 6!! Nice!
Sent from my SGH-I727 using Tapatalk 2
Working on cm10 nightlies
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Hyperrunner said:
Working on cm10 nightlies
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Omg yes hyperrunner! Loved your ROM when I had my nexus 7
Sent from my SGH-T999 using Tapatalk 2
thomas.raines said:
ParanoidAndroid 2.50
CM10
slim bean 2.8
orothus 6
Waiting for feedback
xperiance aokp r3
liquid RC 5
Click to expand...
Click to collapse
Nice to see you around Thomas.
Add R4INS AOKP JB 10/24 to the list. A little scary at first but it all worked out. lol Flashed from ska8ers v6.0.1.3 Wiped caches then flashed zip. After a few seconds screen went blank and phone was totally unresponsive. Never a fun sight when flashing a kernel as you know. Waited a bit then rebooted using the power button hold trick. After rebooting it booted in the OS and I confirmed the kernel indeed flashed. Everything seems to be working fine. No idea what caused the hiccup. Thanks for including the cache/dalvik wipe in the install script as well. I'll let you know in a few days how battery shapes up.
Gonna stay on the skyrocket for a while, might consider making a ROM
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
I can confirm it works on Car vs Drivers cm10 on a Hercules
Sent from my iPad 2 (and I'm not proud of it-_-)
iNeedICS said:
I can confirm it works on Car vs Drivers cm10 on a Hercules
Sent from my iPad 2 (and I'm not proud of it-_-)
Click to expand...
Click to collapse
Yup for pa on hercules
Sent from my Paranoid SGH-T989 with KKO
Hyperrunner said:
Gonna stay on the skyrocket for a while, might consider making a ROM
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
please do all devs are welcome and looking at your work it seems like you put out some quality builds
thomas.raines said:
ParanoidAndroid 2.50
CM10
slim bean 2.8
orothus 6
Waiting for feedback
xperiance aokp r3
liquid RC 5
Click to expand...
Click to collapse
confirm. not work on liquid Rc5 . maybe that build is 10-11 which is too old .
This is an Unoffical port of SlimBean ROM for our device. I had no part of the development, I only compiled it.
{
"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"
}
This is lightweight and fast JellyBean 4.2.2 AOSP-based, with tweaks from CM10.1 and AOKP. I like it as it is a powerful ROM with many settings and options but without feeling too bloated with features that many don't use. You won't find a PIE option or Per-App dpi settings here, but you will find many customizations to make this run exactly as you see fit. Here's some of what it offers:
-8 Lockscreen targets
-Notification bar and drawer transparency settings
-Custom carrier label
-Battery bar
-CM Power Widget
-Hardware key custom actions (including back button)
-Disable lockscreen widgets and/or usability hints
-Quiet Hours
-DashClock Widget built in
-Widgets Viewpager (a kind of locker at the bottom of the screen for widgets that can be called by a hardware -key assignment, very cool)
-linaro -O3 flags
-Dark Slim option (a built in theme to darken everything)
-much more...
Changelog
SlimBean 7-24-13 Nightly
One last build for Android 4.2 (4.3 is already being merged)
Latest nightly for SlimBean 7.5
Option to have incoming calls stay in backround.
Fixed commandline tools (i.e bash not working right)
SlimBean 7-22-13 Nightly
Updated sources to latest 7.5 build
Added some minor fixes and more commandline tools
7-18-13 Nightly
7-18-13 Nightly with xtra APN for LTE taken from here
Latest nightly for SlimBean 7.2
Fixes to TRDS messenging text colors.
Storage Settings: Allow user to trigger a volume rescan
Backup: Use native google backup system to backup profile feature
Latest nightly for SIimBlean 7.0
Voicemail no longer dials *86
Statusbar Quick Peek option (swipe down to view in full screen modes)
Mem fixes
Dashclock Updates
Gapps updated (linked below)
Linaro -O3 optimizations
Latest CM 3.4 kernel from Cyanogenmod sources
Be sure to use the Slim Gapps (linked below), they are toggleable for use with The Real Dark Slim
5-10-13 Nightly -
Latest nightly for SlimBean v5.1
Now includes a second level for PIE
Nova launcher included by default
Changes to MMS and Recent Apps Switcher
More optimizations
New kernel tweaks for better performance
Enjoy
5-6-13 Rebase
This is a rebase of the 4-25-13 Build. After a long battle, the camera is now fully functional, enjoy.
4-25-13 Nightly -
Latest codefreeze for Slimbean 4.2.2 Build 4.2
Switched back to Cyanogenmod sources for kernel
Fixed headphone detection on ROM side, switching kernels won't break it anymore!
Default dpi is 240 (can be easily switched back to 320)
Apks optimized, reducing memory and hopefully better multitasking.
cLock is added back in.
Integrated, resource-friendly PIE, which allows for custom assignments (including apps)
Assign Button Action to hardware menu key longpress in Lockscreen
Fixed "void endpwent()" error for sshd
Built with better linaro -O3 handling
Switched to Evervolv's kernel
Also more stuff that I'm forgetting. Enjoy!
NOT WORKING IN THIS VERSION: camera/video -- See the newer builds above, this has been fixed.
4/11/13 Nightly -
-Removed default music app and added Apollo
-Added Launcher2 tweaks by JamieG71 (will feel much snappier)
-Compiled busybox with linaro -O3 flags (may increase speed)
-Added CM LockClock back in, for those that don't like DashWidget
-Fixed bash error "void endpwent()(3) is not implemented on Android", good riddance!
-Compiled command-line utilities: ssh, scp, netcat, openvpn, rsync, and htop into ROM
-Added Terminal emulator into build
-Added a few other tweaks I'm forgetting here
THIS BUILD IS VERY SMOOTH AND SNAPPY, ENJOY!!
4/5/13 Nightly
-First release. Compiled kernel with linaro -O3 flages, swapped in my themed blue DeskClock, added extra alarm rington for some morning madness..
Credits:
kushdeck For making CM possible on the Jewel device, his kernel source is what is powering this ROM. His endless hours of work are much appreciated.
SlimRoms They really put together an amazing ROM.
jamieg71 His roms motivated me to start compiling my own, and his help allowed my to dive into adding linaro toolchains.
thicklizard For giving me a fix for a problem of headphones not being connected, wouldn't have gotten this without him.
Evervolv Using their sources helped fix some errors I was running into when porting this.\
I do not own this phone, thanks to Dustin, pside15, jrior001for testing this for me
Downloads:
Gapps:
Slim gapps
These Slim Gapps are recommended for use with this ROM, they are in an Aroma installer and feature the toggleable Gapps (for a Google apps dark look when The Real Dark Slim option is toggled)
Misc:
SlimBean offical add-ons (this ROM comes slimmed down and many things are available as an addon, email is located in the Extras package).
4.2 Camera with Photosphere This zip name is camera42patchedv2.zip, does anyone know the creator of it? I can't give proper credit as I downloaded it a while back and don't remember from where.. sorry
4.3 Camera Flash the 4.2 Photosphere zip above and then install this like any other apk. Works great!
Hints
Enable Developer Settings: goto Settings --> About Phone --> Build Number, and click 7 times
Enable Rebot Menu (Reboot Recovery, Reboot Bootload, etc), goto Settings --> Developer Options --> Advanced Reboot, pick one
If you prefer the stock lockscreen handle, here is a link to set it to stock.
Explore their website, there are many add-ons for this ROM
Enjoy!
-Mike
** HOW-TO COMPILE THIS YOURSELF **
Here are my notes on how to port SlimBean to our devices, should anyone be interested in compiling their own. I ran into a few headaches when I attempted this, so I’m hoping these notes will save others from that. The point of this tutorial is to teach newbies how to port a ROM, while I could do some things on my end make it easier to compile this ROM, I think it's important to outline all the steps involved in doing this by hand, so the methods may be applied to other ROM ports, not just SlimBean.
I compiled on a Debian Wheezy system, 64bit (squeeze should be the same). A 64-bit computer is required to compile Jellybean (ICS and above for that matter), so don’t attempt this on anything less. If you are unfamiliar with installing Debian, you can use LMDE, it's a live Debian system that you can install with minimal linux knowledge and works pretty nice. However the installation process is pretty easy for vanilla Debian and a good learning process, so give it a shot if you have the time.
Do this all as root
Download dependencies:
Code:
apt-get install git-core gnupg flex bison gperf build-essential zip curl libc6-dev libncurses5-dev x11proto-core-dev libx11-dev libreadline6-dev g++-multilib mingw32 openjdk-6-jdk tofrodos python-markdown libxml2 libxml2-utils schedtool pngcrush xsltproc zlib1g-dev lib32stdc++6 lib32ncurses5 ncurses-libs.i686 libstdc++.i686 libgcc.i686 lib32readline-gplv2-dev lib32z1-dev
Link files:
Code:
ln -s /lib32/libncurses.so.5 /lib32/libncurses.so
or for Ubuntu 10.10:
Code:
sudo ln -s /usr/lib32/mesa/libGL.so.1 /usr/lib32/mesa/libGL.so
Install Google’s repo script:
Code:
mkdir ~/bin
PATH=~/bin:$PATH
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod 755 ~/bin/repo
Make your working Directory and start syncing with SlimBean
Code:
mkdir ~/slimbean; cd ~/slimbean
repo init -u git://github.com/SlimRoms/platform_manifest.git -b jb4.2
repo sync
Create a local_manifests file with Cyanogenmods sources for our phone and kernel (thanks to Deck’s work). This is porting part.
Code:
mkdir ~/slimbean/.repo/local_manifests
echo ‘<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- CyanogenMod -->
<project name="CyanogenMod/android_device_htc_evita" path="device/htc/evita" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_device_htc_s4-common" path="device/htc/s4-common" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_device_htc_msm8960-common" path="device/htc/msm8960-common" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_kernel_htc_msm8960" path="kernel/htc/msm8960" remote="github" revision="cm-10.1" />
<!-- Add HTC Proprietary Files -->
<project name="TheMuppets/proprietary_vendor_htc" path="vendor/htc" remote="github" revision="cm-10.1" />
<!-- Add qcom-caf source for our phone -->
<project path="hardware/qcom/media-caf" name="SlimRoms/hardware_qcom_media-caf" remote="github" revision="jb4.2" />
<project path="hardware/qcom/display-caf" name="SlimRoms/hardware_qcom_display-caf" remote="github" revision="jb4.2" />
<project path="hardware/qcom/audio-caf" name="SlimRoms/hardware_qcom_audio-caf" remote="github" revision="jb4.2" />
<!-- Add personal fixed bash -->
<remove-project name="SlimRoms/android_external_bash" />
<project path="external/bash" name="mikshepard/android_external_bash" remote="github" revision="cm-10.1" />
</manifest>’ > ~/slimbean/.repo/local_manifests/evita.xml
Sync the repo again
Code:
repo sync
Create your device file for Slimbean (adapted from CM’s cm.mk file):
Code:
echo '# Specify phone tech before including full_phone
$(call inherit-product, vendor/slim/config/gsm.mk)
# Release name
PRODUCT_RELEASE_NAME := evita
# Boot animation
TARGET_SCREEN_HEIGHT := 1280
TARGET_SCREEN_WIDTH := 720
# Inherit some common CM stuff.
$(call inherit-product, vendor/slim/config/common_full_phone.mk)
# Inherit device configuration
$(call inherit-product, device/htc/evita/device_evita.mk)
# Device naming
PRODUCT_DEVICE := evita
PRODUCT_NAME := slim_evita
PRODUCT_BRAND := htc
PRODUCT_MODEL := One X
PRODUCT_MANUFACTURER := HTC
# Set build fingerprint / ID / Product Name etc.
PRODUCT_BUILD_PROP_OVERRIDES += PRODUCT_NAME=htc_evita BUILD_FINGERPRINT=cingular_us/evita/evita:4.1.1/JRO03C/131981.6:user/release-keys PRIVATE_BUILD_DESC="3.18.502.6 CL
# Copy compatible prebuilt files
PRODUCT_COPY_FILES += \
vendor/slim/prebuilt/hdpi/bootanimation.zip:system/media/bootanimation.zip' > ~/slimbean/device/htc/evita/slim.mk
then create a vendorsetup.sh file
Code:
echo “add_lunch_combo slim_evita-userdebug” >> ~/device/htc/evita/vendorsetup.sh
now we build our environment:
Code:
. build/envsetup.sh
get a list of all devices:
Code:
lunch
Choose slim_evita-userdebug (it should be option 9), and then create your ROM:
Code:
make bacon
when finished, it’ll be located in ~/slimbean/out/target/product/evita/
NOTE: if using a multi-core processor use "make -jX bacon" where X = the number of cores you have. For my duel-core processor, I use "make -j2 bacon".
TIP:
If you are into building, checkout my acompile script in my signature, it'll email you when your build is complete using Gmail's snmp and will include the time it took and the last few lines of the output. I find it very useful for knowing when my build is done (especially since they take me about 3+ hours apiece)
SOURCES:
This page helped a lot with a great tutorial on building ROMS
This forum is filled with great people who others with the building of ROMS. A great source when you run into errors you don’t understand.
Hope this helps someone,
-Mike
Sweet... I was wanting to try to bring this to Evita but haven't had much time. Thanks man, downloading now
Sent from my One X using Tapatalk 2
Thank you.
another ROM to try out..
Nicely done. I work entirely too much right now. Lol.
I had plans to bring this to evita and actually have source downloading right now for it, guess I can cancel that.
I'm going to have to try this out, very, very soon.
Sent from my HTC One X using xda premium
Gonna give this a try mik. I was working on it as well but never got close to getting it to compile. For you other crack flashers Im working on getting a Rootbox build up in a few days.
Sent from my HTC One X using Tapatalk 2
Oh the flashing never ends Trying this one out now
Very pleased with this ROM. The NFC switch actually works without a reboot and I'm not getting any weird frame buffer jitters like on the current unofficial CM10.1. Thank you for getting this running on the One X!
Sent from my One X using Tapatalk 2
Geez... It's raining ROMs! :victory: Definitely going to give this a shot!
I know it's early - but folks that are flashing this - please keep us posted on battery life.
neocryte said:
I know it's early - but folks that are flashing this - please keep us posted on battery life.
Click to expand...
Click to collapse
It should be pretty similar to other aokp roms..
neocryte said:
I know it's early - but folks that are flashing this - please keep us posted on battery life.
Click to expand...
Click to collapse
I will go ahead and let it settle in for two days and post about it on Saturday afternoon (Eastern).
Sent from my One X using Tapatalk 2
Glad everyone is enjoying this ROM, it's my favorite to use. So many features, yet not very bloated, it's extremely well done. I wouldn't worry about battery life guys, it's been great on my Jewel device and since we share the same kernel, it should be same for the Evita. Flash and enjoy
Cheers,
Mike
Can't wait to try this tonight :thumbup:
Sent from my One XL using XDA Premium
Went to go download some add ons and the slimrom site links aren't working? Anyone else having this problem?
Mosch26 said:
Went to go download some add ons and the slimrom site links aren't working? Anyone else having this problem?
Click to expand...
Click to collapse
+1
Sent from my HTC One X using xda app-developers app
sropedia said:
+1
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
They're working again for me. That's just odd that they were not working last night
FYI, the zip to reset the lock screen handle to stock did not work for me.
Sent from my One X using Tapatalk 2
vn1977 said:
FYI, the zip to reset the lock screen handle to stock did not work for me.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Hmm.. that's odd, it worked fine for me. Can anyone else confirm?
-Mike
mikshepard said:
Hmm.. that's odd, it worked fine for me. Can anyone else confirm?
-Mike
Click to expand...
Click to collapse
Disregard... I had somehow downloaded the one from the FAQ on the slimroms site that was different than the one linked. The one linked on the OP worked, although when I rebooted "gapps" FC'd, but nothing seems affected by it. Thank you!
Sent from my One X using Tapatalk 2
{
"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:
/*
*** Disclaimer
* Your warranty is now void.
*
* I am not responsible for bricked devices,
* 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.
*/
Introduction:
I have been using xda-developers.com for almost 3 years and getting all the benefits. I feel its time for me to pay back. Its my small contribution to the android world.
Slim7, based on nougat 7.1.1, is now available for download! I will try to publish the updated versions whenever i have time. Please do not expect a weekly release.
Click to expand...
Click to collapse
Features:
Interface
Status Bar
Recent apps panel
Navigation
Onscreen Navigation bar & tweaks (long press + double tap)
Hardware button tweaks (long press + double tap)
Display
Ambient Display == Ferrari Doze
Security
Advanced reboot menu
General
SlimLauncher
SlimDim
SlimActions and shortcuts
In-call vibration features
Theme manager for substratum type of themes
Click to expand...
Click to collapse
Sources: https://github.com/Ferrari-Dev-Team/
Thanks to:
Google
SlimRoms
Cyanogenmod
xda-developers
@dh.harald
@Rohan purohit
@thewisenerd
@faizauthar12
and all the developers who has contributed to android
Click to expand...
Click to collapse
XDA:DevDB Information
Slim7, ROM for the Xiaomi Mi 4i
Contributors
anbuchelva, thewisenerd, faizauthar12, Rohan purohit
Source Code: https://github.com/SlimRoms
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: 8.x.x.x
Based On: ASOP
Version Information
Status: Beta
Current Beta Version: 0.19
Beta Release Date: 2017-04-10
Created 2016-08-03
Last Updated 2017-04-10
Changelogs
Download folder link: https://www.androidfilehost.com/?w=files&flid=88778
Slim-Ferrari-7.1.1 build.0.19
Code:
[B]Change log: [/B]
Detailed change logs here: [URL="https://slimroms.org/"]https://slimroms.org/[/URL] refer posts
[LIST]
[*]Slim7 Beta 0.19
[*]Slim7 Beta 0.18
[*]Slim7 Beta 0.17
[/LIST]
Device Specific : enabled signature spoofing, so people can use nogapps/microg/nanomode.
Slim-Ferrari-7.1.1 build.0.16
Code:
[B]Change log: [/B]
Initial release in Android 7.1.1_r26 version
Slim-Ferrari-6.0.1.build.1.3
Code:
[B]Change log: [/B] from [URL="https://slimroms.org/"]https://slimroms.org/
[/URL]Merge android-6.0.1_r66
Frameworks/av: libcameraservice: Don't pass NULL args on setCallbacks call
Frameworks/base: Prevent invocation of startNavigating() when GPS is off
Frameworks/base: am: Account for time changes when showing recent activities
Frameworks/base: SystemUI: fix 'Contents hidden' notification text color in dark mode
Fix notification for Ebay, Inbox and Slack in dark mode
Automatic translations updates
Add bluetooth battery status when available
Fix missing location tile on lockscreen
Correct charging sounds string
Fix possible NPE upon screen rotation
DeviceKeyHandler: Fix suspend gesture not working
System/core: libutils: fix deadlock in elapsedRealtimeNano
Slim-Ferrari-6.0.1.build.1.1
Code:
[B]Change log:
Slim:[/B]
Frameworks/av: libstagefright: mtk: Use vendor extensions to check if we should fixup cropping
Hardware/qcom/audio-caf/msm8916: hal: Fix compilation with verbose debugging enabled and policy_hal: Fix build with Clang
Hardware/qcom/display-caf/msm8916: display: Fix warnings on 64-bit clang
Updates to hardware/qcom/media-caf/msm8916
Updates and fixes to frameworks/base
SlimRecents: Fix header text default color & Correct default bg color
SlimLauncher: Fix launcher default_workspace taking up all apps button location & Materialize search bar and add night mode
Updates to frameworks/av and frameworks/native
Packages/apps/Settings: PGM: Permute simple and long click behaviour
Theme GooglePackageInstaller, Gmail, and hangouts for night mode
Keyguard: fix dark text in carrier and message areas
Fix battery icon not following light status bar
Cast Tile: only scan while in detail view
Revert clock to the right in demo mode if in center or left
Bunch of navbar fixes (transparency, dimension options not working, and show in landscape, lag)
Fix QS tile filter utility
Fix some qs issues ( editor not following dark mode, add icons to add dialog, and fix remaining black text in detail view)
Fix reset button on hwnav settings
Fix Slim Action Shortcuts
Fix lights out buttons shift
Slim recents: number of max apps not sticking (Recycle SlimSeekBarPreference view)
Fix missing 'none' action
Fix reset icon inconsistencies
[B]Ferrari device specific:[/B]
[URL="http://github.com/ferrari-dev-team"]http://github.com/ferrari-dev-team[/URL]
Slim-ferrari-6.0.1.build.1.0 - file has been deleted due to mobile network bug
Slim-ferrari-6.0.1.alpha.0.9
Change log:
Code:
-Slim change logs are here: [URL="https://slimroms.org"]https://slimroms.org[/URL]
[B]Ferrari change logs:[/B]
-Kernel tweaks - fixes lagging issue
[B]Bug:[/B]
-snap cam fc on video recording. Flash snapdragon camera 2.1 as an alternative
-you tell me
Slim-ferrari-6.0.1.alpha.0.8
change log:
Code:
- August security updates
- Initial addition for custom QS
- Fix on SOD
- Enable on screen menu
- updates on the kernel
Slim-ferrari-6.0.1.alpha.0.7
change log:
Code:
[B]New features:[/B]
In-call vibration features
Statusbar clock and date customizations
Battery icon and text
SlimRecents
Slim NavBar with double tap function
Started to include Snap on devices
[B]Changes[/B]
Updates to device/qcom/common
Fixes to dark theme UI elements
Updates to frameworks/av
Updates to frameworks/native
Hardware/qcom/audio-caf/msm8960: Revert 'hal: Add support for AUDIO_DEVICE_OUT_LINE'
System/netd: Don't build the QSAP SDK on Nexii
Flashing Instructions:
Boot into recovery
Make a backup
Wipe data, system, cache, dalvik/art cache
flash firmware 8.x.x.x (if you are using 6.x.x.x firmware)
flash rom.zip
flash gapps.zip (optional)
Reboot
Click to expand...
Click to collapse
Important Notes:
If you need root, flash super-su or Magisk
opengapps is recommended (i'm using pico)
forward all feature requests to [url]https://slimroms.org/[/URL]
be polite to other members
Keep your discussion away from this thread if it is relating to substratum - slim theme engine
I'll try to update this rom whenever I have time. Do not ask for ETA.
Click to expand...
Click to collapse
Alternate URL for the firmware
AFH
for developers
local_manifest.xml file contains:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/xiaomi/ferrari" name="anbuchelva/android_device_xiaomi_ferrari" remote="github" revision="slim7.1"/>
<project path="kernel/xiaomi/ferrari" name="ferrari-dev/android_kernel_xiaomi_ferrari" remote="github" revision="n/dtb.stock"/>
<project path="vendor/xiaomi/ferrari" name="anbuchelva/proprietary_vendor_xiaomi_ferrari" remote="github" revision="cm-14.1" />
<project name="lineageos/android_device_cyanogen_msm8916-common" path="device/cyanogen/msm8916-common" remote="github" revision="cm-14.1" />
<project name="TheMuppets/proprietary_vendor_qcom_binaries" path="vendor/qcom/binaries" remote="github" revision="cm-14.1" />
<project name="lineageos/android_external_stlport" path="external/stlport" remote="github" revision="cm-14.1" />
<project name="lineageos/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" revision="cm-14.1" />
<project name="lineageos/android_external_bson" path="external/bson" remote="github" revision="cm-14.1" />
</manifest>
Special thanks to
@Rohan purohit - have spent numerous hours to bring nougat for ferrari
@thewisenerd - for the firmware and CAF kernel
@faizauthar12 - for being a kid and for the support
Great, another new build!!!
thanks
cool bro
flashed this rom, getting several sod while idle..
imagine92 said:
flashed this rom, getting several sod while idle..
Click to expand...
Click to collapse
Noted.. try using Sensei kernal, didn't have any sod from the evening. Anyway, I'll try to fix in the next build.
anbuchelva said:
Noted.. try using Sensei kernal, didn't have any sod from the evening. Anyway, I'll try to fix in the next build.
Click to expand...
Click to collapse
which sensei version? using latest version sensei can't record video
New rom cool
Sent from my MI 4i using XDA-Developers mobile app
@anbuchelva
Sorry for the issue
It should be fixed now ,try to make a new kernel and test it
imagine92 said:
which sensei version? using latest version sensei can't record video
Click to expand...
Click to collapse
Yea.. I recommended to use it for time being.. I can compromise video recording but not SOD
new build is up, link updated in post#2
i couldn't test it for a long time as i am using AOSP-OMS build.. it would be great if someone tests and provide feedback.
what about camera quality?
Installed this ROM. Good Looking. Not Incredably smooth. Camera quality is good.
Landscape status bar dropdown is a bug? Detailed review after 2 days.
New build is up.. see post #2 for download link
anbuchelva said:
New build is up.. see post #2 for download link
Click to expand...
Click to collapse
The last build with sensei kernel is super awesome except camera bug. Recently flashed 0.8, so I will flash again if 1.0 is released.
BTW Is nav bar issue fixed? Enabling soft keys is not disabling hardware keys. I used some workarounds but I am not satisfied with it.
Good work.
Nihhaar said:
The last build with sensei kernel is super awesome except camera bug. Recently flashed 0.8, so I will flash again if 1.0 is released.
BTW Is nav bar issue fixed? Enabling soft keys is not disabling hardware keys. I used some workarounds but I am not satisfied with it.
Good work.
Click to expand...
Click to collapse
Not yet, is an upcoming feature..
new build is up.. change logs will be updated soon. flash at your own risk!!
Hey guys. In 6 years of using Android I have compiled some Roms, but now I'm stuck, cause I haven't compiled a Rom with a non-existent device tree.
I just followed the tutorial http://forum.xda-developers.com/showthread.php?t=1863547 till the point, where it tells you to make the device specific changes, where you'll have to setup device.mk, device.removes etc. Which repos exactly do I have to insert there, to get a functional device tree?
I haven't got any help in the AOSPA-irc other then posting the tutorial, which I just followed.
As a base I would use the Omnirom kernel, vendor files etc, as they are stable and also based on AOSP
This is my local_manifest/vendorfiles.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="DonkeyCoyote/proprietary_vendor_motorola"
path="vendor/motorola" remote="github" revision="android-6.0" />
<project name="omnirom/android_device_motorola_clark"
path="device/motorola/clark" remote="github"
revision="android-6.0" />
<project name="omnirom/android_hardware_qcom_display-caf-msm8992"
path="hardware/qcom/display-caf-msm8992" remote="github"
revision="android-6.0" />
<project name="omnirom/android_hardware_qcom_media-caf-msm8992"
path="hardware/qcom/media-caf-msm8992" remote="github"
revision="android-6.0" />
<project name="omnirom/android_hardware_qcom_audio-caf-msm8992"
path="hardware/qcom/audio-caf-msm8992" remote="github"
revision="android-6.0" />
<project name="omnirom/android_device_qcom_caf-sepolicy"
path="device/qcom/sepolicy" remote="github"
revision="android-6.0" />
<project name="omnirom/android_frameworks_av"
path="frameworks/av-caf"
remote="github" revision="android-6.0-caf" />
<project name="omnirom/android_frameworks_native"
path="frameworks/native-caf" remote="github"
revision="android-6.0-caf" />
<project name="omnirom/android_hardware_ril"
path="hardware/ril-caf"
remote="github" revision="android-6.0-caf" />
<project name="omnirom/vendor_qcom_opensource_dataservices"
path="vendor/qcom/opensource/dataservices" remote="github"
revision="android-6.0" />
<project name="omnirom/android_kernel_motorola_msm8992"
path="kernel/motorola/msm8992" remote="github"
revision="android-6.0" />
<project name="omnirom/android_hardware_sony_thermanager"
path="hardware/sony/thermanager" remote="github"
revision="android-6.0" />
<project name="omnirom/android_hardware_sony_timekeep"
path="hardware/sony/timekeep" remote="github"
revision="android-6.0" />
<project name="omnirom/android_packages_apps_SnapdragonCamera"
path="packages/apps/SnapdragonCamera" remote="github"
revision="android-6.0" />
<project name="omnirom/android_external_libnfnetlink"
path="external/libnfnetlink" remote="github"
revision="android-6.0" />
<project name="omnirom/android_external_libnetfilter_conntrack"
path="external/libnetfilter_conntrack" remote="github"
revision="android-6.0" />
</manifest>
Try using a device tree from an asop ROM with Clark or a cm one
But this doesn`t generate me the files that are mentioned here:
Create /manifest/<device>.adds
* Create /manifest/<device>.removes
* Create /prebuilt/pa_<device>.conf
* Create /products/pa_<device>.mk
* Add device makefile entry to /products/AndroidProducts.mk
* Create /vendorprops/<device>.proprietaries
* Add device lunch menu entry to /vendorsetup.sh
Otherwise lunch, breakfast and brunch wouldn`t find clark.
Here is where I got stuck. I couldn't work on it because in Turkey we have this thing called Fair Quota Usage and after 250gigs DL speed drops all the way from 50 Mbps to 3.
This is my Local_Manifest file:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="purenexus-clark/android_device_motorola_clark" path="device/motorola/clark" remote="github" revision="mm2" />
<project name="AICP/kernel_motorola_msm8992" path="kernel/motorola/msm8992" remote="github" revision="mm6.0" />
<project name="AOSPB/hardware_ril" path="hardware/ril-caf" remote="github" revision="mm6.0-caf" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_hardware_qcom_bt" path="hardware/qcom/bt-caf" remote="github" revision="cm-13.0-caf" />
<project name="CyanogenMod/android_hardware_sony_thermanager" path="hardware/sony/thermanager" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_hardware_sony_timekeep" path="hardware/sony/timekeep" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_system_qcom" path="system/qcom" remote="github" revision="cm-13.0" />
<project name="purenexus-clark/proprietary_vendor_motorola" path="vendor/motorola" remote="github" revision="mm2" />
</manifest>
Click to expand...
Click to collapse
I tried to use this guide: http://forum.xda-developers.com/showthread.php?t=1863547
I have synced the marshmallow branch, then added the local manifest and synced once again. Things got ugly when I tried adding device support especially in the Device Specific Changes part, because the guide is a bit outdated I guess. I have used extract-files.sh for prebuilts & additional props and there was no issue. There is no manifest folder in vendor/pa/ so I couldn't create /manifest/<device>.adds and also # Create /manifest/<device>.removes and Create /prebuilt/pa_<device>.conf.
In Create vendor/pa/products/pa_<device>.mk part the folder is rearranged (every device has it's own folder so I created a clark folder and written pa_clark.mk and pa.dependencies (I have no idea if dependencies is right because I have no idea about it) here are the codes:
pa_clark.mk:
# Check for target product
ifeq (pa_clark,$(TARGET_PRODUCT))
# Include ParanoidAndroid common configuration
TARGET_BOOT_ANIMATION_RES := 1440
include vendor/pa/main.mk
# Inherit AOSP device configuration
$(call inherit-product, device/motorola/clark/pa_clark.mk)
# Override AOSP build properties
PRODUCT_NAME := pa_clark
PRODUCT_BRAND := Google
PRODUCT_MODEL := X Pure
PRODUCT_MANUFACTURER := Motorola
PRODUCT_BUILD_PROP_OVERRIDES += \
PRODUCT_NAME=clark \
BUILD_FINGERPRINT=google/clark/clark:6.0.1/MTC20F/3031278:user/release-keys \
PRIVATE_BUILD_DESC="clark-user 6.0.1 MTC20F 3031278 release-keys"
endif
Click to expand...
Click to collapse
pa.dependencies:
[
{
"remote": "github",
"repository": "purenexus-clark/android_device_motorola_clark",
"target_path": "device/motorola/clark",
"revision": "mm2"
},
{
"remote": "github",
"repository": "AICP/kernel_motorola_msm8992",
"target_path": "kernel/motorola/clark",
"revision": "mm6.0"
},
{
"remote": "github",
"repository": "CyanogenMod/android_hardware_qcom_bt",
"target_path": "hardware/qcom/bt-caf",
"revision": "cm-13.0-caf"
},
{
"remote": "github",
"repository": "AOSPB/hardware_ril",
"target_path": "hardware/ril-caf",
"revision": "mm6.0-caf"
},
{
"remote": "github",
"repository": "CyanogenMod/android_device_qcom_common",
"target_path": "device/qcom/common",
"revision": "cm-13.0"
},
{
"remote": "github",
"repository": "CyanogenMod/android_hardware_sony_thermanager",
"target_path": "hardware/sony/thermanager",
"revision": "cm-13.0"
},
{
"remote": "github",
"repository": "CyanogenMod/android_hardware_sony_timekeep",
"target_path": "hardware/sony/timekeep",
"revision": "cm-13.0"
},
{
"remote": "github",
"repository": "CyanogenMod/android_system_qcom",
"target_path": "system/qcom",
"revision": "cm-13.0"
},
{
"remote": "github",
"repository": "purenexus-clark/proprietary_vendor_motorola",
"target_path": "vendor/motorola",
"revision": "mm2"
}
]
Click to expand...
Click to collapse
I have done the exact same in Add device makefile entry to /products/AndroidProducts.mk part. There is no vendor/pa/vendorprops/ folder so I had to skip Create /vendorprops/<device>.proprietaries part. I have also done Add device lunch menu entry to /vendorsetup.sh part as well.
So for the building part:
I had to delete hardware/ril directory because it was giving me the error that there is already a RIL folder but Im trying to use the RIL that's given by you. now when I write ./rom-build.sh clark it gives me this error:
make: *** No rule to make target 'out/target/product/clark/kernel', needed by 'out/target/product/clark/boot.img'. Stop.
make: *** Waiting for unfinished jobs....
Click to expand...
Click to collapse
If you want, here is the full code.
http://pastebin.com/1FSxyFz7
---------- Post added at 10:16 AM ---------- Previous post was at 09:51 AM ----------
Hashbang173 told me that it doesn't compile the kernel but I couldn't continue because I built a new PC and I couldn't recover VM file because I made it fixed size (200gb) and the only ssd I use 240gb so I will start from scratch in the beginning of the October.
Maybe we could build PA together.
You could manually create this folder:
as user: mkdir /vendor/pa/manifest
I will edit my local_manifests file to match yours, but building with omnirom sources, cause aicp cause some bootloops for some users and they have to go back to stock and that`s the issue, why I haven`t tried out AICP for month.
Thanks for your help
OCmylife said:
Maybe we could build PA together.
You could manually create this folder:
as user: mkdir /vendor/pa/manifest
I will edit my local_manifests file to match yours, but building with omnirom sources, cause aicp cause some bootloops for some users and they have to go back to stock and that`s the issue, why I haven`t tried out AICP for month.
Thanks for your help
Click to expand...
Click to collapse
The only ROM I have worked with is CM so I'm pretty much a newbie in this as well. I will pm you when I start working on it because I want PA as well!
I will start from scratch, fork all the necessary repos into my github-account and create and compare the needed files for compiling with the ones that are used for the 5X. Maybe this will get us to a working AOSPA build. Just pm me, when you are ready : :good:
So let`s clean this up a bit.
I`ve "fixed" the
Code:
make: *** No rule to make target 'out/target/product/clark/kernel', needed by 'out/target/product/clark/boot.img'. Stop.
make: *** Waiting for unfinished jobs....
error by copying my boot.img from omnirom to out/target/product/clark/kernel/
But now I get my next error, which is waiting:
Code:
no rule to make target „out/target/product/clark/obj/STATIC_LIBRARIES/lib_driver_cmd_qcwcn_intermediates/export_includes“, needed by "out/target/product/clark/obj/EXECUTABLES/hostapd_intermediates/import_includes“
I couldn`t get this issue fixed for now.
OCmylife said:
So let`s clean this up a bit.
I`ve "fixed" the
Code:
make: *** No rule to make target 'out/target/product/clark/kernel', needed by 'out/target/product/clark/boot.img'. Stop.
make: *** Waiting for unfinished jobs....
error by copying my boot.img from omnirom to out/target/product/clark/kernel/
But now I get my next error, which is waiting:
Code:
no rule to make target „out/target/product/clark/obj/STATIC_LIBRARIES/lib_driver_cmd_qcwcn_intermediates/export_includes“, needed by "out/target/product/clark/obj/EXECUTABLES/hostapd_intermediates/import_includes“
I couldn`t get this issue fixed for now.
Click to expand...
Click to collapse
have you seen this? http://androidforums.com/threads/rom-cm10-boost-force-wip.763908/page-6
Yep, doesn't work for me. I think, that there are missing repositories. I've added hardware/qcom/wifi but still no fix.
Damn. There is not much of a solution I could find as well. The guides are so outdated.
I was testing and compiling from 8am to 2pm today and I really need a break. I think that we need a more experienced person to help us with this stuff, but maybe you have more luck :fingers-crossed:
I'll try this friday as well. Try to rest, if I learned one thing from this, it's that it never ends
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"
}
Hello guys, We have been working over a week now and we just managed to get to the first boot. We will keep working and port remaining stuff!
ereneren564 said:
Hello guys, We have been working over a week now and we just managed to get to the first boot. We will keep working and port remaining stuff!
Click to expand...
Click to collapse
Just here to say that PA was my favorite rom on my OPO, if this continues along I'll def be using it!!! Thanks for the amazing work!:good:
jerpd3rp said:
Just here to say that PA was my favorite rom on my OPO, if this continues along I'll def be using it!!! Thanks for the amazing work!:good:
Click to expand...
Click to collapse
Right now RIL doesn't work. When we manage to fix that we will release the rom I believe.
ereneren564 said:
Right now RIL doesn't work. When we manage to fix that we will release the rom I believe.
Click to expand...
Click to collapse
I hope so!
Update: We have added the gestures of the phone and the most important thing that needs to be fixed is RIL.
1st step in the right direction thanks to @bgos10
delete (double post)