Downloads:
Newest KLTE release - https://drive.google.com/open?id=0B47RFUwP7JMWUno4Umo3QjVqSHM
{
"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"
}
News:
Update 6th of January 2017: ROM compiled, testet, seems to work fine. Shared with you guys: https://drive.google.com/open?id=0B47RFUwP7JMWeFd3OGRkSGdhU2s
Update 5th of January 2017: All you people with modem/baseband issues (SIM-card not working); follow these steps: https://forum.xda-developers.com/showpost.php?p=70365379&postcount=3017 - @haggertk 's LineageOS is now my daily driver thanks to these instructions. But i am currently compiling my own ROM.
Update 2nd January 2017: Rmwolf's Lineage ROM gave the the SIM-card not detected problem. Went for @haggertk 's version, and the same problem there: https://forum.xda-developers.com/ga...m-cyanogenmod-14-0-galaxy-s5-android-t3476433
Update 30th December 2016: @rmwolf has done a test-compile: https://drive.google.com/open?id=0B977dasK1YVnM2gtWjlyal8zNFU
Initial thread text 29th December 2016:
Hi all,
I've been following the Lineage OS website the last couple of days, and i think it's interestering following the progress here: http://review.lineageos.org even though i don't understand a whole lot of it.
I have a background in compiling ROM's back in the day for the LG P880, and i barely remember pulling source files from Github and compiling my own ROM's. Unfortunately i do not have the internet line for it right now. I might be able to experiment a bit with it when i get back to work next week though.
But what happens if we follow the CM guides like this:
http://reventlov.com/tutorials/portable-hacking/how-to-build-cyanogenmod-for-huawei-ideos-u8150
And slightly modify the process, so it get's the source from here:
https://github.com/LineageOS/android_device_samsung_klte
..and finally, a HUGE thanks to @haggertk for making this possible!
Would also like to link to this news post:
http://lineageos.org/Infrastructure-Status-and-Official-Builds/
Where they say:
As a reminder: we have not started doing official builds yet. One of the benefits of this being an open source project is that anyone can build it, but please be careful flashing builds you’ve downloaded from other sources. We will have some more information on when weeklies (or possibly nightlies) will be starting soon.
So.. It might be ready to build?
I need to say hello to someone who came from p880 I had it too.
So if you want to compile LineageOS, I think all you need is renamed CM's repos. That's what I have from CM14.1 builds:
local_manifest.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_samsung_klte" path="device/samsung/klte" remote="github" />
<project name="CyanogenMod/android_device_samsung_klte-common" path="device/samsung/klte-common" remote="github" />
<project name="CyanogenMod/android_device_samsung_msm8974-common" path="device/samsung/msm8974-common" remote="github" />
<project name="CyanogenMod/android_kernel_samsung_klte" path="kernel/samsung/klte" remote="github" />
<project name="CyanogenMod/android_external_stlport" path="external/stlport" remote="github" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" />
<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" />
</manifest>
roomservice.xml:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/hudson" path="hudson" remote="github" revision="master" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-14.1"/>
<project name="haggertk/cm_build_stuff" path="cm_build_stuff" remote="github" revision="cm-14.1" />
</manifest>
You have to repo init first. Try repo init -u http://github.com/LineageOS/Android.git -b cm-14.1. Then add local_manifest file and then run breakfast/make breakfast (idk right now). As I have seen from cm14.1 thread Lineage 7.1.1 won't differ much from CM14.1...
Hope it helps, report back and ask if you need more help
EDIT: for note: https://github.com/LineageOS/android_build/commit/8a2e40068c2cd7eeaac8f15cedd848f1d93724d2
LGaljo said:
I need to say hello to someone who came from p880 I had it to.
So if you want to compile LineageOS, I think all you need is renamed CM's repos. That's what I have from CM14.1 builds:
local_manifest.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_samsung_klte" path="device/samsung/klte" remote="github" />
<project name="CyanogenMod/android_device_samsung_klte-common" path="device/samsung/klte-common" remote="github" />
<project name="CyanogenMod/android_device_samsung_msm8974-common" path="device/samsung/msm8974-common" remote="github" />
<project name="CyanogenMod/android_kernel_samsung_klte" path="kernel/samsung/klte" remote="github" />
<project name="CyanogenMod/android_external_stlport" path="external/stlport" remote="github" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" />
<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" />
</manifest>
roomservice.xml:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/hudson" path="hudson" remote="github" revision="master" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-14.1"/>
<project name="haggertk/cm_build_stuff" path="cm_build_stuff" remote="github" revision="cm-14.1" />
</manifest>
You have to repo init first. Try repo init -u http://github.com/LineageOS/Android.git -b cm-14.1. Then add local_manifest file and then run breakfast/make breakfast (idk right now). As I have seen from cm14.1 thread Lineage 7.1.1 won't differ much from CM14.1...
Hope it helps, report back and ask if you need more help
Click to expand...
Click to collapse
Hi LGaljo, nice to see other remembering the P880.
Thanks for the tip. I actually prepared myself for some negative feedback, so i am really excited to see your contribution here. I will get a Linux machine up running when i get back to work next week, and try it out. The whole building process is starting to come back to me now when i see your code here.
Lineage OS for klte (Galaxy S5 Intnl)
I have built Lineage OS for klte (Samsung Galaxy S5 International) and will test it later today. Let me know if I should upload the ROM
@nixuser1980 : good, if you upload LOS for KLTE i'll be more than happy to give a try. I can't build up a compiler now.
Link for LineageOS 14.1 - Samsung klte
rmwolf said:
@nixuser1980 : good, if you upload LOS for KLTE i'll be more than happy to give a try. I can't build up a compiler now.
Click to expand...
Click to collapse
I am waiting for XDA to allow me to post links. Apparently, I will need 10 posts. I sent the link to you instead, perhaps you would like to re-post.
Here is the link. Downloading now for testing purposes. Let you know if I'll survive . Thankyou.
nixuser1980 said:
https://drive.google.com/open?id=0B977dasK1YVnM2gtWjlyal8zNFU
Click to expand...
Click to collapse
---------- Post added at 10:44 AM ---------- Previous post was at 10:28 AM ----------
Ok, flashed. Obviously it takes a while to boot up, but no issues by now.
To remain IN-Topic, it could be a good idea if you share the set-up of the compiler, as it works as it should.
rmwolf said:
Here is the link. Downloading now for testing purposes. Let you know if I'll survive . Thankyou.
---------- Post added at 10:44 AM ---------- Previous post was at 10:28 AM ----------
Ok, flashed. Obviously it takes a while to boot up, but no issues by now.
To remain IN-Topic, it could be a good idea if you share the set-up of the compiler, as it works as it should.
Click to expand...
Click to collapse
Brief Setup Instructions:
$ mkdir -p ~/bin
$ mkdir -p ~/android/system
<Download repo binary as per previous CM instructions>
$ chmod a+x ~/bin/repo
$ repo init -u <LineageOS github link> -b cm-14.1
$ repo sync
$ source build/envsetup.sh
$ breakfast klte
At this point, we need to modify $HOME/android/system/.repo/local_manifests/roomservice.xml and add the following items:
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-14.1" />
<project name="TheMuppets/proprietary_vendor_qcom_binaries" path="vendor/qcom/binaries" remote="github" revision="cm-14.1" />
$ repo sync (yes, again - to ensure that we have downloaded all of the required proprietary items from TheMuppets - thanks to them)
If you plan to reuse the source repository, consider adding this to $HOME/.bashrc for a compile speed-up:
export USE_CCACHE=1
And then in future compiles:
$ prebuilts/misc/linux-x86/ccache/ccache -M 50G
Now to commence the actual build:
$ croot
$ brunch klte
Please let me know if there are any errors or omissions. Also, please note that the source repo is about 30G and that the build system, Jack is sensitive to RAM availability due to its heap. You may need to perform something like the following if Jack loses its connection to its server:
$ export JACK_SERVER_VM_ARGUMENTS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx7000m"
My previous builds of CM sometimes failed due to the lack of a gello apk prebuilt. You will need to add this if your build fails to have maven download the apk and hash files (md5, sha1)
Awesome!! I hope you don't mind i include the link for the ROM in the topic rmwolf?
Downloading now, and going to try later tonight.
faabak said:
Awesome!! I hope you don't mind i include the link for the ROM in the topic rmwolf?
Downloading now, and going to try later tonight.
Click to expand...
Click to collapse
Not a problem for me, we have to ask to nixuser1980, btw.
faabak said:
Awesome!! I hope you don't mind i include the link for the ROM in the topic rmwolf?
Downloading now, and going to try later tonight.
Click to expand...
Click to collapse
No problem, please do.
faabak said:
Awesome!! I hope you don't mind i include the link for the ROM in the topic rmwolf?
Downloading now, and going to try later tonight.
Click to expand...
Click to collapse
Here there. Its great that you are building it but I talked to a guy who was building unofficial nightlies for some devices and I asked him to build for klte too. He said that he will add it tonight and from tomorrow you can get unofficial nightlies from his site.
Here is the adress. Look for klte when it shows up tomorrow. Also he said that he will open an unoffical thread for it too. So lets wait for it. In the mean time if you guys have any other supported devices you can get the builds.
btw here is the website
and here is the method to build lineageos from scratch.
KLTE page up now!
Lineage-14.1-20161231-UNOFFICIAL-klte.zip
I have mixed impressions after installing this ROM on 2 klte phones of same type (SM-G900F).
Actually the ROM (lineage-14.1-20161231-UNOFFICIAL-klte.zip) runs smooth on one of my S5 klte (a SM-G900F) devices now.
So I installed it also on the S5 klte that I mainly use (that also is a SM-G900F).
The first one is running without problems all seems to work no issues.
The second one will not recognize my SIM-card and keeps rebooting randomly (I did a clean install wiping all data and system etc.)
First one is equipped with a SIM-card from KPN Netherlands.
Second one is equipped with a SIM-card from Vodafone Libertel Netherlands.
I can't re-install my backup in TWRP recovery to return to CM (the 24t December version) on the second one.
Because TWRP aborts recovery mentioning that my modem is mounted read only (which is not the case).
This is the TWRP message:
Restore Complete
Failed
Updating partition details…
…done
Full SELinux support is present.
MTP Enabled
Restore folder: ‘/external_sd/TWRP/BACKUPS/41659be0/2017-01-01
Skipping MD5 check based on user setting.
Calculating restore details…
Cannot restore Modem – mounted read only.
Strange that two identical phones have different behaviour after installing Lineage OS. To me it's unlikely that that this can be caused by a SIM-card from different providers. But this is the only difference between the two phones now exept that the first phone was running Cyanogenmod 14.1 from December 16 2016 and the second phone was on Cyanegonmod from December 24 2016.
Does anyone here have a solution?
It would be great if someone can help me out here.
nixuser1980 said:
I have built Lineage OS for klte (Samsung Galaxy S5 International) and will test it later today. Let me know if I should upload the ROM
Click to expand...
Click to collapse
How about updating to lineageos from cm14, will it receive update via integrated updater or i should download lineageosrom.zip and then flash it? If i flash it over cm14 - it should be factory reseted and wiped - so all apss and conf are gone afterwards?
Is there official release of lineageosrom for s5?
Got the SIM-card problem myself when trying this. CM also had this on the 25-12 ROM. Dirtyflashed back to CM 24-12, and it was working again.
So i guess some phones get the SIM-card problem, and some does not..?
dzincha said:
How about updating to lineageos from cm14, will it receive update via integrated updater or i should download lineageosrom.zip and then flash it? If i flash it over cm14 - it should be factory reseted and wiped - so all apss and conf are gone afterwards?
Is there official release of lineageosrom for s5?
Click to expand...
Click to collapse
I am currently using LineageOS Unofficial on my klte, flashed over CM14.1, without factory reset (only Dalvik cache wipe). I am not aware of any official releases at this point and am trying to get LineageOS 14.1 running on grouper. I don't know lineageosrom.zip.
---------- Post added at 12:28 PM ---------- Previous post was at 12:25 PM ----------
faabak said:
Got the SIM-card problem myself when trying this. CM also had this on the 25-12 ROM. Dirtyflashed back to CM 24-12, and it was working again.
So i guess some phones get the SIM-card problem, and some does not..?
Click to expand...
Click to collapse
Sounds like it... I have had no issues with this yet but can't build a good grouper ROM to save myself.
https://forum.xda-developers.com/ga...m-cyanogenmod-14-0-galaxy-s5-android-t3476433
I have bug on s5 klte with cm14 - screen rotation doesn't work. Sensor is alive - tested in sensors apk.
Otherwise all is great. Battery life much better than with stock. Only downside that power saver goes off after reboot or recharge - i would like to have it always on
dzincha said:
I have bug on s5 klte with cm14 - screen rotation doesn't work. Sensor is alive - tested in sensors apk.
Otherwise all is great. Battery life much better than with stock. Only downside that power saver goes off after reboot or recharge - i would like to have it always on
Click to expand...
Click to collapse
It does work; it just doesn't seem to be very predictable. It can take a while for LineageOS to realise the phone has been rotated but once it's rotated once, there's no stopping it; subsequent rotations seem to be detected immediately until you stop rotating for a period of time again.
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"
}
Android 4.1.2
ParanoidAndroid 2.57.6
Source compiled
You can follow the PA-JB Progress for Galaxy Nexus in this thread: http://forum.xda-developers.com/showthread.php?t=1619582
Follow Paranoid Android officially on:
Facebook : https://www.facebook.com/paranoidgoogle
Twitter : https://twitter.com/paranoid_team
G+ : http://goo.gl/e3tKJ
Prolog
This is NOT a port.
This is the FIRST PA ROM that is built from source for GT-N7000 and I'm providing these builds on a nightly basis when there is changes from CM or PA.
Latest build
$ 67c732c11c83ae263cabd2f7f7b5b1a5 pa_n7000-2.57.6-20130422-155555-Utacka.zip
> Download link: http://goo.im/devs/Utacka/n7000
When updating always make a copy of your /etc/paranoid/properties.conf before flashing, just in case. If restore dont work push this after flashing, restore permission and reboot.
Gapps: http://goo.im/gapps/gapps-jb-20121011-signed.zip
Extras: For custom Kernels and other goodies, click here. (under construction)
AOSP alternatives to touchwiz apps (Note that the list is updated on my n7100 thread so don't derp and write n7000 stuffs there)
Previous builds
$ 27735501f8112b7e98fde30059b56baa pa_n7000-2.57.4-20130306-233340-Utacka.zip
$ ba022e647514658361cdde30491408f0 pa_n7000-2.57.3-20130226-191844-Utacka.zip
$ 8c88f7d1cb92b978ced36b3661b029e0 pa_n7000-2.57.2-20130210-124649-Utacka.zip
$ 342d25c4cfc8d52ccfa3fb9fae21b14d pa_n7000-2.57-20130110-155538-Utacka.zip
$ 277696e95d6066f9eab7597af20ac50d pa_n7000-2.56-20121229-133307-Utacka.zip
$ 7d541f647614bb3c2dc9d885f853d0d5 pa_n7000-2.56-20121220-092537-Utacka.zip
$ c317221bdc25aff07f3d358f6f031140 pa_n7000-2.56-20121216-223502-Utacka.zip
$ 6aa048cd5ffca94a143fc0e64b39a31b pa_n7000-2.56-20121212-095600-Utacka.zip
$ b4ef858f9cd8c8c9f39e2ee43a4ca70c pa_n7000-2.55-20121209-173905-Utacka.zip
$ b29fa5b593e478b586c43dfbdc694b63 pa_n7000-2.55-20121207-112352-Utacka.zip
$ 8930a044e030dab678bd575693b715cf pa_n7000-2.55-20121204-165445-Utacka.zip
$ 8658826a649c0a9c8e7cb3d636eda087 pa_n7000-2.55-20121201-114327-Utacka.zip
$ 675d3eb2a4eba6d67ce0f93a7ca6abf2 pa_n7000-2.55-20121130-162243-Utacka.zip
$ 74c7fc675842616754477d72c69cee4b pa_n7000-2.55-20121126-100801-Utacka.zip
$ ebf412f16dfa74e23565233ef7c25959 pa_n7000-2.55-20121124-103140-Utacka.zip
$ b9d34adf103e8914e7006630e1e6f4a5 pa_n7000-2.55-20121119-165937-Utacka.zip
$ cf5a040d4dd4a47e83ee26b61d132473 pa_n7000-2.55-20121117-122551-Utacka.zip
$ 4990210308f5b3ef1864f99c3672e7c3 pa_n7000-2.54-20121114-155006-Utacka.zip
Githubs:
https://github.com/Utacka
https://github.com/ParanoidAndroid
https://github.com/CyanogenMod
Usefull links
[GUIDE] Which Kernels are Safe/Unsafe to Wipe and Flash from
[GUIDE] How to install § backup § revert CM/AOKP rom [β]
Kernel Repository
[Modem] All Radio's at 'One' Place
[HELP CENTER] How to prevent § handle wakelocks § save battery life[GUIDE] [β]
CM gerrit
PA gerrit
Special thanks to
PARANOIDANDROID team
CYANOGENMOD team
be_vigilant
Chasmodo
g.lewarne
AA1973
sam.crowther
Find any combination you like, scale and project apps, widgets and system components!
PER-APP-COLOR, Paranoidandroids newest invention. Define apps in your regular hybrid panel (same that allows you to scale apps individually and choose their interface). See your phone fade into the color definition of your current app, press home or go elsewhere and it fades back. Create as many combinations you like, you can even dabble with opacity. This feature is made possible by our hybrid engine, which is unique to this rom.
To be honest, this is not tablet mode at all, it has nothing to do with silly build.prop hacks. This is the first and only Android rom to feature true Hybrid mode. This rom lets you scale and project every app, every widget, even systemcomponents individually. Remember, android is modular, everything is an app: Lockscreen, navigationbar, dialogs, popups, keyboards, widgets, and your regular apps of course. Apps have the capability to switch into various designs or layouts according to the device they run on. This can result in a complete new experience as many apps will transform to the better.
Now for every element that you like chose a mode (PhoneUI, Phablet/Nexus-7UI, TabletUI) and/or a size. You are 100% independent of the system DPI which runs nicely in whatever value it has been assigned to. You do not need to boot your phone into a certain DPI. Neither will most of the changes you apply require a reboot. You will not suffer from the myriads of troubles which normally haunt you under build.prop tablet mode. Your market, phone, etc. will all work, apps won't shrink on you unless you shrink them yourself. This project will entirely transform your device, but retain the aesthetics and the feel of your phone.
Donations to molesarecoming
to D4rKn3sSyS
to Cyanogenmod
Make sure to run CM9/10 or an AOSP-based ROM : FLASHING FROM STOCK ICS OR ROMS BASED ON STOCK ICS WILL RESULT IN A BRICK! - You're warned!
[GUIDE] Which Kernels are Safe/Unsafe to Wipe and Flash from <- READ THIS IF YOU ARE CONFUSED
CWM: YOU NEED TO FULLWIPE IF YOU ARE COMING FROM ANOTHER ROM
CWM: Install Zip: Rom: http://goo.im/devs/Utacka/n7000
CWM: Install Zip: Gapps: http://goo.im/gapps/ (latest gapps-jb and even when updating to new PA build)
Reboot and edit your Apps Dpi & Layout under Settings/Paranoid Settings - DO NOT RESTORE YOUR OLD PROPERTIES FOR NOW
If you want to explore the various phone modes, tap "Configuration," chose an option, wait for it to finish, then do a manual reboot
Video tutorial: http://www.youtube.com/watch?v=72Ow-YQeex4
pa webpage: http://www.paranoid-rom.com/
You want to port PA? Take a look here: http://forum.xda-developers.com/showthread.php?p=27558806
Go to Settings, System, Font size, set it to NORMAL
Check "Auto Hide" in Settings, System, Statusbar, to finally get Fullscreen
Trebuchet Settings: margins:SMALL, show permanent searchbar:YES, Grid: 4x4, resize all widgets:YES, Wallpaper scrolling: OFF
Paranoid Android Wallpapers: HERE
If you have an issue and you want to call our attention, here's what you do:
1. Try everything you can, find solutions for yourself. Wipe caches, revert all your settings you have made, go back to your stock Kernel, factory reset if you have to or reflash the rom. Assume that the issue is on your side and try your best to isolate it.
2. Search this thread and Cyanogenmods aswell (its our base) for possible reoccurences of your issue and hopefully solutions that may have come up.
3. If you think the issue is important enough that we should cease our work and look into it, post your issue, BUT ...
... stay friendly, do not demand anything, do not threaten
... explain your issue as precise as you can, name the exact apps and conditions that cause trouble, help us to replicate the issue right away. If we can't there's no way we can fix it and your post will simply clutter the thread
... collect evidence, keep in mind this is a developer thread so even if you are not one, do us the favor and research how to record logcat. logcat is the single most important help you can give us to resolve your issue.
Paranoid Android Devs
Cyanogenmod Team
You can find the kernel and device source at the CyanogenMod Github
Official GT-N7000 rom
If you appreciate this download please press the Thanks Button to show your appreciation!
How to set the workspace mode
How to change an apps Layout and size
http://paranoid-rom.com/forum/changelogs-news
Auto update CWM paranoid config restore file
xda member phedders have created a config file to make pa setings stick on upgrading, wanna try it out? click here.
Lost root?
Flash CWM-SuperSU-v0.96.zip.
Pdroid (will fix info when im home)
Manifest:
Code:
<project name="CyanogenMod/android_device_samsung_n7000" path="device/samsung/n7000" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_device_samsung_galaxys2-common" path="device/samsung/galaxys2-common" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_kernel_samsung_smdk4210" path="kernel/samsung/smdk4210" remote="github" revision="jellybean" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" revision="jellybean" />
Ancient builds
$ 55e1f39718f678ca482645c692d5e0c5 pa_n7000-2.54-13NOV2012-005103-Utacka.zip
$ 5cc10bbb5aa93b51ce01f65ff056c6ee pa_n7000-2.54-11NOV2012-173502-Utacka.zip
$ 0ba3151b24c74aa46dd32e4fdd28c3e6 pa_n7000-2.54-10NOV2012-130520-Utacka.zip
$ a0e9d2e3c622e9f0fc19769281eb8e57 pa_n7000-2.54-09NOV2012-004454-Utacka.zip
$ 3ea5b3e3b8d513f26d8aaca8271cf3d9 pa_n7000-2.53-07NOV2012-094914-Utacka.zip | Pulled
$ 891c4bc575cc1a5941fdc45ff350bfa4 pa_n7000-2.53-06NOV2012-135018-Utacka.zip
$ c993a9b40f5b8989be482864be51477f pa_n7000-2.53-05NOV2012-125144-Utacka.zip
$ 5888c556564b5498766489eb105e41e5 pa_n7000-2.53-04NOV2012-054214-Utacka.zip
$ 9cff4a74722a66487413e18f7beef195 pa_n7000-2.52-03NOV2012-022323-Utacka.zip
$ 252a27ea086d2418384ea846d3cafe8b pa_n7000-2.52-01NOV2012-172851-Utacka.zip
$ 6d7de14c6c924d78acaef4a7db033364 pa_n7000-2.52-29OKT2012-101254-Utacka.zip
$ a602eb3742fa10448289ebbb25e5c4a7 pa_n7000-2.52-27OKT2012-150632-Utacka.zip
$ 755025d30be6350c651fb347eaf85331 pa_n7000-2.51-26OKT2012-124415-Utacka.zip
$ b66968ace6c1ad1d604cfd19d1ea6421 pa_n7000-2.51-25OKT2012-000243-Utacka.zip
$ 9a384e4d3c467ab0cca21f3fa9bbb26b pa_n7000-2.50-24OKT2012-115024-Utacka.zip
$ e7d622b2de5a8f3cb2df322eb2391d10 pa_n7000-2.50-23OKT2012-002453-Utacka.zip
$ e4007d8836444c6dc970c3ea3bf3a5f8 pa_n7000-2.23-22OKT2012-122801-Utacka.zip
$ c75be6dc8fc0a5b7823be9c650c0276b pa_n7000-2.23-21OKT2012-145731-Utacka.zip
$ 55d825770f288bcb9857e16518998338 pa_n7000-2.23-20OKT2012-155154-Utacka.zip
$ 0d34d24bfb5db0481c0cf6547a1f5b74 pa_n7000-2.23-19OKT2012-163705-Utacka.zip
$ 8ad31633efbc3964d110d69114e98d90 pa_n7000-2.23-18OKT2012-181625-Utacka.zip
$ ab77ee9f61ceac1bffeeaff35d295ac9 pa_n7000-2.22-17OKT2012-121239-Utacka.zip
$ 2ca43a4d0fdc7fb7f67a685e0c59c472 pa_n7000-2.22-16OKT2012-142038-Utacka.zip
$ 93b95f5e7ed4ac2cc6ad732f0ecd5681 pa_n7000-2.21-15OKT2012-155720-Utacka.zip
$ 5acb00614c423f16bcec5b2e7b3b73a8 pa_n7000-2.21-14OKT2012-210328-Utacka.zip
$ f5b97f5beef4f0409ecc3b6e04b8c2a8 pa_n7000-Utacka-13OKT2012-125511.zip
$ 5e1f2bacc64b26b2f580699d0bf5a75d pa_n7000-Utacka-12OKT2012-130009.zip
$ ee1075d171c3ce6629b50e0be6cc2588 pa_n7000-Utacka-10OKT2012-100128.zip
$ 6c9440545ea66b6efd15193cee1b520d pa_n7000-Utacka-09OKT2012-013535.zip
$ 4622ce5c69df2cb74eb7c70d8ef8277b pa_n7000-2.18-08OKT2012-112955-Utacka.zip
$ 61b2a219e48f397913fa49c1b81d3489 pa_n7000-2.17-07OKT2012-134132-Utacka.zip
$ 99357646bdfb03ffe8d3fb94c6dcbf8b pa_n7000-2.17-05OKT2012-124038-Utacka.zip
$ 45edbd12656502411d8ec8953dfc3942 pa_n7000-2.17-04OKT2012-122726-Utacka.zip
$ 28dbb84644a8c7baf77cf7fb53ff0a14 pa_n7000-2.17-03OKT2012-135923-Utacka.zip
$ ccd17bad5369848fa64f800aff6b94ee pa_n7000-2.17-02OKT2012-122733-Utacka.zip
$ 7b13c4e594b2a50ca1fe585ee82639c6 pa_n7000-2.16-29SEP2012-105218-Utacka.zip
$ e23e20b51989f4f1b6ba2c4078c8c0f3 pa_n7000-2.15-27SEP2012-134234-Utacka.zip
$ 5a50be1529aa8d5714b23e81344dfc32 pa_n7000-2.15-26SEP2012-134343-Utacka.zip
$ c309f489b254a75b218a029a4bba1ac9 pa_n7000-2.15-25SEP2012-144656-Utacka.zip
$ 1b7c495840af7ef269bd8ec2c3b22371 pa_n7000-2.14-24SEP2012-125905-Utacka.zip
$ pa_n7000-2.14-22SEP2012-061603-Utacka.zip - md5: 217c836e0926e34c4ba88a66e9855549 - changelog
$ pa_n7000-2.13-20SEP2012-120953-Utacka.zip - md5: 8bb845c2f5ff24c83cbf97b077414943 - changelog
$ pa_n7000-2.13-19SEP2012-094430-Utacka.zip - md5: ec031e712a0a99c372eacaed5503ea4b - changelog
$ pa_n7000-2.13-18SEP2012-122802-Utacka.zip - md5: a86700535aadd71d3b3a488e613c6499 - changelog
$ pa_n7000-2.13-17SEP2012-143054-Utacka.zip - md5: c9d6acad046e50f4aa1c619febe39585
$ pa_n7000-2.12-16SEP2012-134137-Utacka.zip - md5: b09f89ce8f39b58c173780886c677128
$ pa_n7000-2.12-15SEP2012-153114-Utacka.zip - md5: 771589f3d5f2a7ca3468dd422c535545
$ pa_n7000-2.11-14SEP2012-102128-Utacka.zip - md5: 5d199b645297cc4701ce47aa213b579a
$ pa_n7000-2.11-12SEP2012-134657-Utacka.zip - md5: 4afca29856a42cc5b34c191a9a967411
$ pa_n7000-2.11-10SEP2012-033024-Utacka.zip - md5: fe38170d688b5f036f0ddf12202c2995
$ pa_n7000-2.10-09SEP2012-112154-Utacka.zip - md5: cf5b332ae70b62cc372d06f0729dcc58
$ pa_n7000-2.10-08SEP2012-122853-Utacka.zip - md5: baa23b339da204cc2bc635915a860f91
$ pa_n7000-2.10-07SEP2012-072701-Utacka.zip - md5: 46012e7cd51bade5c0581bfc2179e4ea
$ pa_n7000-2.00-06SEP2012-015710-Utacka.zip - md5: 9e9c00331b7219e166b15e54d8d8beca
BETA RELEASES
Only beta releases will be posted in post #6.
THIS IS EXPERIMENTAL BETA, YOU ARE WARNED
Will be updating beta once or twice a week.
Cherry-pick: [WIP] Stylus gestures features (1/2) (Added to 17OCT beta build)
Cherry-pick: [WIP] Stylus gestures features (2/2) (Added to 17OCT beta build)
Warning to users: This patchset has an UGLY permissions hack in it, the security consequences of it are currently unknown. There's a reason it is still WIP. (Quote by Entropy512)
Warning to users: This patchset has an UGLY permissions hack in it, the security consequences of it are currently unknown. There's a reason it is still WIP. (Quote by Entropy512)
Warning to users: This patchset has an UGLY permissions hack in it, the security consequences of it are currently unknown. There's a reason it is still WIP. (Quote by Entropy512)
Do NOT flash beta if you don't understand this.
Goo will NOT notify a BETA release if you are on regular release.
Goo will ONLY notify you when there is a new BETA release and not the regular if you are on a beta.
Latest build
$ 75825e21b28b92b0d4655b2a0854c5bd pa_n7000-2.22-17OKT2012-035657-beta-Utacka.zip
> Download link: http://goo.im/devs/Utacka/n7000/beta
Previous builds
$ 097c14d9b549427b6924c6dbfd9ccabd pa_n7000-2.16-29SEP2012-113506-beta-Utacka.zip
$ 5f2a12567f06e4272f6057ad2311631e pa_n7000-2.15-28SEP2012-125717-beta-Utacka.zip
nice work~Utacka.
ParanoidAndroid Settings\apps\settings can't preview,if you click preview,you will return to settings.
i am using apex launcher,
but when i reboot,
i don't know how to express my English is terrible.
thank you do this for us.
Hopefully yours will be the most stable JB built... wish you all the best looking forward to the ROM it self.
Sent from my GT-N7000 using xda app-developers app
gr8
pm coming
Heavy duty man flash it when im home ...
Sent from my GT-N7000 using XDA Premium HD app
Gotta flash this now!
Sent from my GT-N7000 using xda premium
Hey bro.
Could you post some more info on your rom?
Like features list and some general description?
Would be nice to know what we are flashing
Thanks a lot for your work
Note sure if we are allowed to call it 2.0 yet?
Post from PA dev here
projeto56 said:
Hey bro.
Could you post some more info on your rom?
Like features list and some general description?
Would be nice to know what we are flashing
Thanks a lot for your work
Click to expand...
Click to collapse
You're flashing a PA/CM10 ROM that is built directly from source..what's there to know? Do you want JB screen shots also?
be_vigilant said:
Note sure if we are allowed to call it 2.0 yet?
Post from PA dev here
Click to expand...
Click to collapse
Thanks for the heads up, it was actually their own makefile that named it 2.00 but ye i can rename OP and post a clearer OP that its not actually 2.00 according to that post.
Edit: As of now official 2.00 is out and new build is up.
Skickat från min GT-N7000 via Tapatalk 2
Utacka said:
Thanks for the heads up, it was actually their own makefile that named it 2.00 but ye i can rename OP and post a clearer OP that its not actually 2.00 according to that post.
Skickat från min GT-N7000 via Tapatalk 2
Click to expand...
Click to collapse
Yup it doesnt help that it auto gets called 2.0 hehe. Thanks for the builds by the way at least this one boots and is from sources rather than my own dirty ports.
Do we need to flash the same gapp from paranoid thread?
Sent from my GT-N7000 using xda premium
Leechoonhwee said:
Do we need to flash the same gapp from paranoid thread?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Same gapps to all CM10 builds, latest currently is: http://goo.im/gapps/gapps-jb-20120726-signed.zip
Now I will finally go and eat something lol
Utacka.. thanks a lot for this ROM..you gave just that one ROM combination I am patiently waiting for!! Thanks a ton again!!
Sent from my GT-N7000 using xda app-developers app
pa_n7000-1.992-05SEP2012-160706.zip uploaded - new build with correct ParanoidPreferences.apk & version on zip
Old one was actually 1.991 ParanoidPreferences.apk, my bad!
Build your 'own' CM10.1 ROM (Android 4.2.1) today!
Revision V1.3 2013.01.09 Updates: No more patching needed. local_manifest.xml updated to new branch revision. Text updates.
Revision V1.2 2012.12.13 Updates: Repo sync branch finally changed from mr1-staging to cm-10.1. Thanks HerrKuk.
Revision V1.1 2012.12.11 Updates: New Patch: WiFi shows networks, BT works, audio.h reworked, notification lights are back, USB mass-storage support included. Compatible to V30A Kernel.
Revision V1.0 2012.12.01 Initial release
Thank you note: Thanks to Ricardo Cerqueira for his work on this device.Thanks to marsgod for BT and WiFi patches/tips.
General note: Please keep in mind that CM10.1 is still experimental. This guide is for those who cannot wait...
{
"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"
}
Preparation
What you need:
You need a fully working build environment. If you don't have one running already, you can follow my guide in the other thread to get a fully working environment under Ubuntu 12.10 64bit. Follow the easy steps in the guide. Make a test build with CM10 to see if it is working. Then you will be ready for the next step.
Your build environment is now set? Good, let's start!
Use the terminal to make the steps. A terminal window can be opened by pressing Ctrl+Alt+T. Every single command for the terminal is marked with a $ sign. Just paste every command (without the $ sign) to your terminal window and there shouldn't be any problem.
Get the sources
Start with creating a new working directory for CM10.1:
Code:
$ mkdir ~/cm10.1
$ cd ~/cm10.1
Initialize Repo for Android CM10.1 (Android 4.2.1):
Code:
$ repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
and enter your credentials if needed.
Download the sources:
Code:
$ repo sync
Wait until it's finished (takes a lot of time!).
If the process hangs use Ctrl+C to break out of it and resume the download with another
Code:
$ repo sync
Initialize the environment
Code:
$ . build/envsetup.sh
Obtain the proprietary files:
Create a file with the name local_manifest.xml in the .repo directory to add additional sources. To see the hidden .repo directory, you have to press Ctrl-H in your file manager.
Create the xml-file with
Code:
$ gedit ~/cm10.1/.repo/local_manifest.xml
20130109: Update! New branch revisions!
Paste the following lines to the editor
Code:
<manifest>
<project name="TheMuppets/proprietary_vendor_lge.git" path="vendor/lge" remote="github" revision="cm-10.1"/>
<project name="CyanogenMod/android_device_lge_p990" path="device/lge/p990" remote="github" revision="cm-10.1"/>
<project name="CyanogenMod/android_device_lge_star-common" path="device/lge/star-common" remote="github" revision="cm-10.1"/>
<project name="CyanogenMod/lge-kernel-star" path="kernel/lge/star" remote="github" revision="cm-10.1"/>
</manifest>
Save the file.
Run another
Code:
$ repo sync
Download the necessary prebuilts from cyanogenmod by running
Code:
$ ~/cm10.1/vendor/cm/get-prebuilts
Ok. That's done!
Patching
20130109: Thanks to Ricardo Cerqueira's Update to the CyanogenMod repos there is no more patching needed!
Only for those who have patched the sources before and want to build with the new sources. If you are new to this skip the 'Patching' part and go to 'Build the ROM' directly.
If you have patched/changed the sources and want to get up-to-date, here is what you can do:
change the local.manifest.xml file that it looks like the one you see above
delete all the directories inside your ~/cm10.1/ directory but keep the hidden .repo directory
repo sync now and the missing files will be downloaded and the whole structure will be recreated without redownloading the repos you already have
get the prebuilts with ~/cm10.1/vendor/cm/get-prebuilts
and this is it, just brunch p990 again
Build the ROM
Code:
$ repo sync
$ brunch p990
and flash it via CWM. Make a clean start (if necessary) with format /system, wipe data/factory reset, etc..
Have fun!
FAQ
Revision V1.5 20130110 New GAPPS, now without the nasty force closing AOSP keyboard 'bug'
Revision V1.4 20130109 Sections updated: bootloader section, Baseband section, partition size, mass storage mode. Sections removed: building smaller ROMs, mobile data connection, Flight mode, WIFI & BT
Revision V1.3 20121214 Updates: New GAPPS from 20121212
Revision V1.2 20121211 Updates: Bluetooth working, WiFi Networks showing and more. Plus typo fixes.
Revision V1.1 20121206 Updates: Partition size, swapping internal/external memory, USB mass-storage mode.
Revision V1.0 20121201 Initial release
Thanks to key.ita, XXMrHyde, tonyp, Custom40 and marsgod for their contributions to this FAQ.
Where are the Google Applications - GAPPS?
Get the fixed GAPPS here. Fix: The 'bugged' gesture typing is disabled. That's due to Tegra2 which isn't supporting NEON instructions. With the fix you can use the keyboard as usual without force closes.
Or you can get the 'original' GAPPS from 20121212 for 4.2.1 here. Download and flash them via CWM.
The keyboard is force closing all the time. Is there a solution?
Yes. Just flash the fixed GAPPS over your installation via CWM. The gesture typing will be disabled but you can use the AOSP keyboard then as you used it in the previous versions. It's up to you but now you can disable the useless gesture trail, dynamic floating preview etc. under 'Settings>>>Language & input>>>Android keyboard AOSP>>>Enable gesture typing'. Then remove the tick from 'Enable gesture typing' and you are ready to use the AOSP keyboard without any problems.
What bootloader should be used?
You have to use the old bootloader.
Any Baseband recommendations?
I am using the 30B Baseband. You can find it in tonyp's Baseband thread under 'ICS Basebands'. But it is working with other BBs like V20L as well.
[/I]
What about the partition size? Will this ROM (including the GAPPS) fit in the old partition layout?
Yes, it does. Some files get copied to /data so the ROM plus GAPPS fit the old partition size completely.
The 'Developer options' from 'settings' are gone. Where are they?
Touch the 'Build number' seven times in 'about phone'. Then they will appear.
How do I use the external SD-Card as the internal memory (swap SD-Cards)?
Edit the 'vold.fstab' file on your phone under 'system/etc/' and change the lines to:
Code:
dev_mount sdcard /storage/sdcard0 auto /devices/platform/sdhci-tegra.2/mmc_host/mmc1
dev_mount emmc /storage/sdcard1 9 /devices/platform/sdhci-tegra.3/mmc_host/mmc0
If you want to use it permanently on your building system and in every ROM you make then edit '~/CM10.1/device/lge/p990/vold.fstab' and use the both lines above accordingly.
I want to transfer files from/to the phone via USB. How do I turn on the mass-storage mode?
Use the terminal on the phone or use adb shell:
Code:
su
setprop persist.sys.usb.config mass_storage
And reboot. When you use your Computer's USB connection the next time, Android will ask you whether you like to switch on the mass-storage mode.
I want to use the mass-storage mode in my builds. What can I do?
I included it in the ROM building process by editing "~/CM10.1/device/lge/star-common/star.mk'. At the very end of the file you find the line 'persist.sys.usb.config=mtp'. Change it to 'persist.sys.usb.config=mass_storage'. Next time you build a new ROM the mass-storage mode is included. Tip: if you are updating your ROM then sometimes you have to make the switch manually (one time only!) as described above to initiate the change.
Are there any other problems?
I think it is awesome!!! Very fast, nice camera, same energy usage as CM10. I am using it as my daily driver. (well, since Nov 28 now... :fingers-crossed
Please build CM10.1 yourself and test it thoroughly. Maybe we can remove some of the remaining problems together.
Reserved for future use
nice guide :silly:
mivv a lazy one....
Are the sources downloading fast? I didn't try Paranoid... You said few coffees... I think I drank a bucket of coffee and it still wasn't there = went to sleep
I'll try, Although I am busy with my pi... that sdcard corruption bug with OC driwes me crazy, I guess I'll ssh my kitchen PC too do something in parallel...
Does this build has the call bug or it's like Benee's hackfest free of it?
and Raum1807 does HW acceleration work?
Will do this guide next week. Just finished REMICS TOUCHWIZ UX now released for everyone. Then Motorola UI... So next week I'll have time
Sent from my Xoom using XDA Premium HD app
Might give this a go myself, but as you said, it's still in pretty early stages of development.
Thanks for the useful guide though
Shouldn't the file's name be local_manifest.xml?
I.e.
Code:
$ gedit ~/cm10.1/.repo/local.manifest
needs to be changed into
Code:
$ gedit ~/cm10.1/.repo/local_manifest.xml
in order for it to work. Right?
svante38 said:
Shouldn't the file's name be local_manifest.xml?
I.e.
Code:
$ gedit ~/cm10.1/.repo/local.manifest
needs to be changed into
Code:
$ gedit ~/cm10.1/.repo/local_manifest.xml
in order for it to work. Right?
Click to expand...
Click to collapse
Of course. Corrected it. Thanks!
puma99dk| said:
Does this build has the call bug or it's like Benee's hackfest free of it?
and Raum1807 does HW acceleration work?
Click to expand...
Click to collapse
HWA is working. It is basically running like CM10.
The call bug hasn't occurred to me (yet). But I think it is the wrong name anyway: in my opinion it is an microphone/audio bug.
In this ROM the RIL and audio are a bit different. So maybe this bug isn't there. But this is a good reason why I would like to see more people building and testing CM10.1.
Raum1807 said:
Of course. Corrected it. Thanks!
Click to expand...
Click to collapse
Also, looking at your patch, it seems to point to directories on your local machine:
Code:
/home/ac64/cm10.1/...
Shouldn't this be changed to:
Code:
~/cm10.1/...
In order for it to work on all computers?
Can someone upload a build of this?
Sent from my LG-P990 using xda app-developers app
svante38 said:
Also, looking at your patch, it seems to point to directories on your local machine:
Code:
/home/ac64/cm10.1/...
Shouldn't this be changed to:
Code:
~/cm10.1/...
In order for it to work on all computers?
Click to expand...
Click to collapse
By applying the patch with the "-p 4" argument, the first 4 "parts" of the path will be ignored,
by typing:
Code:
cd ~/cm10.1
patch -p4 < CM10.1_building.patch
the path will be "set" correct.
It`s a better to do it this way, so the patch is working also if your path to your repo is different,
e.g. your repo path is CM10.1/android/system/
you have to type:
Code:
cd ~/cm10.1/android/system/
patch -p4 < CM10.1_building.patch
But you can change the path in the CM10.1_building.patch to ~/CM10.1...
but in this case, you have to change the -p4 argument to -p0, or just apply the patch without -p argument
XXMrHyde said:
By applying the patch with the "-p 4" argument, the first 4 "parts" of the path will be ignored,
by typing:
Code:
cd ~/cm10.1
patch -p4 < CM10.1_building.patch
the path will be "set" correct.
It`s a better to do it this way, so the patch is working also if your path to your repo is different,
e.g. your repo path is CM10.1/android/system/
you have to type:
Code:
cd ~/cm10.1/android/system/
patch -p4 < CM10.1_building.patch
But you can change the path in the CM10.1_building.patch to ~/CM10.1...
but in this case, you have to change the -p4 argument to -p0, or just apply the patch without -p argument
Click to expand...
Click to collapse
Oh I see. Thanks for clearing that up.
Thanks OP for the building instructions too, teaching people to fish instead of just providing them one!
Raum1807 said:
HWA is working. It is basically running like CM10.
The call bug hasn't occurred to me (yet). But I think it is the wrong name anyway: in my opinion it is an microphone/audio bug.
In this ROM the RIL and audio are a bit different. So maybe this bug isn't there. But this is a good reason why I would like to see more people building and testing CM10.1.
Click to expand...
Click to collapse
I highly doubt a magic fix
Sent from my Optimus 2X using xda app-developers app
Custom40 said:
Might give this a go myself, but as you said, it's still in pretty early stages of development.
Thanks for the useful guide though
Click to expand...
Click to collapse
if you get it done, please share
last i have test a CM10.1 from EaglesBlood and there work no camera and BB28g has no Signal... would in this CM10.1 all fixed??
See the Screenshots in post #1, signal is working,
just building CM10.1, will report if camera is working
MetaIIica said:
last i have test a CM10.1 from EaglesBlood and there work no camera and BB28g has no Signal... would in this CM10.1 all fixed??
Click to expand...
Click to collapse
EaglesBlood is not CM, its based on AOSP.
Hey all!
If you have noticed, on ICS/JB there is a little transition when you click on a chooserbox. This is a nice feature which I like very much!
After doing some investigation on framework I realized that on res/drawable-mdpi there were some pngs which are needed for this feature to work.
{
"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"
}
Click to expand...
Click to collapse
Actually this feature exists on gingerbread but there aren't enough xmls to activate it. Seems like Google has abandoned the project because of some reasons. The closest reason is this :
"Google have not implemented the full sources of it because they wanted to reserve it for future releases. [On ICS/JB]"
Why do i think so? Because @SpaceCaker has discovered many secrets whose nature is like in our case. He has discovered weather information on lockscreen, Music Player Control on Lockscreen and also some codes and smalis which are present on ICS.
[Actually, I have used custom sources rather than using google's one]
Today I gonna show you how to fully implement it on GB! :victory:
Requirments :
-APK Multi Tools
-Notepad++
-Knowledge about xmls
-Sources on attachments
Click to expand...
Click to collapse
- Decompile framework-res.apk
1. Go to res/drawable/list_selector_background.xml
You will see something like this :
Code:
<?xml version="1.0" encoding="utf-8"?>
<selector
xmlns:android="http://schemas.android.com/apk/res/android">
<item android:state_window_focused="false" android:drawable="@color/transparent" />
<item android:state_focused="true" android:state_enabled="false" android:state_pressed="true" android:drawable="@drawable/list_selector_background_disabled" />
<item android:state_focused="true" android:state_enabled="false" android:drawable="@drawable/[B]list_selector_background_disabled[/B]" />
[COLOR="red"]<item android:state_focused="true" android:state_pressed="true" android:drawable="@drawable/list_selector_background_transition" />
<item android:state_focused="false" android:state_pressed="true" android:drawable="@drawable/[B]list_selector_background_transition[/B]" />[/COLOR]
<item android:state_focused="true" android:drawable="@drawable/list_selector_background_focus" />
</selector>
2. Change the 2 red lines. It will look like this :
Code:
<?xml version="1.0" encoding="utf-8"?>
<selector
xmlns:android="http://schemas.android.com/apk/res/android">
<item android:state_window_focused="false" android:drawable="@color/transparent" />
<item android:state_focused="true" android:state_enabled="false" android:state_pressed="true" android:drawable="@drawable/list_selector_background_disabled" />
<item android:state_focused="true" android:state_enabled="false" android:drawable="@drawable/list_selector_background_disabled" />
[COLOR="Red"]<item android:state_focused="true" android:state_pressed="true" android:drawable="@drawable/[B]sniper_killer[/B]" />
<item android:state_focused="false" android:state_pressed="true" android:drawable="@drawable/[B]sniper_killer[/B]" />[/COLOR]
<item android:state_focused="true" android:drawable="@drawable/list_selector_background_focus" />
</selector>
3. Download the Highlight Chooserbox_source.zip in the attachment, extract it and put sniper_killer.xml on drawable folder.
It consists these lines :
Code:
<item android:duration="20" android:drawable="@drawable/sniper_status_bar_item_pressed_anim2" />
<item android:duration="20" android:drawable="@drawable/sniper_status_bar_item_pressed_anim2" />
<item android:duration="30" android:drawable="@drawable/sniper_status_bar_item_pressed_anim3" />
<item android:duration="30" android:drawable="@drawable/sniper_status_bar_item_pressed_anim4" />
<item android:duration="40" android:drawable="@drawable/sniper_status_bar_item_pressed_anim5" />
<item android:duration="50" android:drawable="@drawable/sniper_status_bar_item_pressed_anim6" />
<item android:duration="60" android:drawable="@drawable/sniper_status_bar_item_pressed_anim7" />
<item android:duration="60" android:drawable="@drawable/sniper_status_bar_item_pressed_anim8" />
4. Put the PNGs on res/drawable-mdpi
5. Recompile framework-res.apk and test
Click to expand...
Click to collapse
Proof :
[The transition changes in miliseconds making it impossible to capture.
But after tries and tries i finally managed to capture the transition ]
Pressed :
Click to expand...
Click to collapse
Selected :
Click to expand...
Click to collapse
Credits :
-ryanfebriyadi
-Google
-Me
Click to expand...
Click to collapse
To devs
Developers, if you decide to use it on your ROM just put my name on the credits! :good:
Leave a thanks if you find this helpful! :good:
Awesome guide bro keep it up :thumbup::thumbup::thumbup:
Sent from my Ace-i
Hitesh2626 said:
Awesome guide bro keep it up :thumbup::thumbup::thumbup:
Sent from my Ace-i
Click to expand...
Click to collapse
Thanks and btw, if you are on SGS3 ROM don't try it as V6 include it and V6 will be out tomorrow
Thanks for the guide! Can it be used on Cm7?
Sent from my GT-S5830i using xda app-developers app
mathm2013 said:
Thanks for the guide! Can it be used on Cm7?
Sent from my GT-S5830i using xda app-developers app
Click to expand...
Click to collapse
Yes! CM7.2 is GB and i said it will work on all GB devices.
Good and Simple Guide, Sniper
Thanks!
:victory:
brijeshep said:
Good and Simple Guide, Sniper
Thanks!
:victory:
Click to expand...
Click to collapse
Thanks!
Awesome guide Sniper... !!! ICS feature for our Little Ace... Good work..!!
Sniper Killer said:
Thanks and btw, if you are on SGS3 ROM don't try it as V6 include it and V6 will be out tomorrow
Click to expand...
Click to collapse
Thanks budddy i know as you had mention it in post before
Thanks
Sent from my Ace-i
Good job, Sniper. Now we have phone with some features ICS/JB on Ace I. :laugh:
Nice and simple Guide Sniper! Awesome work!
Ok. Good work, but what about guide for add ics/jb wifi and bluetooth togless in main menu settings?
Sent from my GT-S5830i using xda premium
misha1996 said:
Ok. Good work, but what about guide for add ics/jb wifi and bluetooth togless in main menu settings?
Sent from my GT-S5830i using xda premium
Click to expand...
Click to collapse
I can make a guide for that too but Its a lil' hard for ya guys
If I do I will try to make it noob friendly.
Sent from my GT-S5830i using Tapatalk 2
Also, today is not only my birthday xD
Today is my Ace-i's birthday too
I bought ace i on the same day like my birthday 1 year ago :laugh:
misha1996 said:
Ok. Good work, but what about guide for add ics/jb wifi and bluetooth togless in main menu settings?
Sent from my GT-S5830i using xda premium
Click to expand...
Click to collapse
Sniper Killer said:
I can make a guide for that too but Its a lil' hard for ya guys
If I do I will try to make it noob friendly.
Sent from my GT-S5830i using Tapatalk 2
Click to expand...
Click to collapse
And it rather requires a unique bug fix
OT
Wish you a happy 'b day , teddy
(completed all my 8 thanks , will press tomorrow )
------OT CLOSED------
Sniper Killer said:
Also, today is not only my birthday xD
Today is my Ace-i's birthday too
I bought ace i on the same day like my birthday 1 year ago :laugh:
Click to expand...
Click to collapse
Happy Birthday!
Your mod works perfectly fine with CM7 as well..Tested! Works like a Charm!
Congratulations, Teddy.
But...write that guide please.
Sent from my GT-S5830i using xda premium
misha1996 said:
Congratulations, Teddy.
But...write that guide please.
Sent from my GT-S5830i using xda premium
Click to expand...
Click to collapse
Can't till we get the permissions :silly:
If you are looking for my nightly builds, you can find them here.
{
"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"
}
NOTE: Official nightly builds for CM 10.2 are now available! Get them here.
Click to expand...
Click to collapse
So after countless hours of frustration and face-desking, I finally managed to make a working build of CyanogenMod 10.2 (Android 4.3). To make the process slightly less painful for you, I've decided to create this noob-friendly guide. This is my first development guide, so feel free to leave criticism or suggestions through PM.
Prerequisites
You will need:
A relatively recent computer running Ubuntu with a reasonable amount of RAM (I recommend at least 4 GB) and around 35 GB of free hard drive storage
A decent internet connection
Some understanding of basic Android and Linux operation and terminology is helpful
NOTE: This guide is for Ubuntu 13.04 x64, but should work with other relatively recent versions of Ubuntu as well; i.e. 12.04, 12.10.
Click to expand...
Click to collapse
Setting up the build environment
The first thing you need to do is install the correct Java Development Kit/JDK, Oracle Java 6. If you have OpenJDK installed, you have to uninstall it by typing this command into the terminal, which can be brought up by pressing Ctrl+Alt+T or searched for in the dash.
Code:
sudo apt-get purge openjdk*
To install Oracle Java 6, type this into the terminal (one line at a time):
Code:
sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get install oracle-java6-installer
y
Android SDK requires the x32 compatability packages, ia32-libs. Install it by entering this:
Code:
sudo apt-get install ia32-libs
y
Now you will need to get the Android SDK/Software Developer Kit, if you haven't already. Go ahead and download it here.
Extract it to a folder of your choice (in this guide, I will refer to it as ~/android/sdk) and from that folder, enter these commands into the terminal:
Code:
cd ~/android/sdk/adt-bundle/sdk/tools
./android sdk
Click Install packages. cd to ~/android/sdk/adt-bundle/sdk/platform-tools and type:
Code:
adb
fastboot
If you've done everything correctly, you should get a big block of text for both (which list all of the adb/fastboot commands).
Next, install the build packages. Copy and paste this command into the terminal:
Code:
sudo apt-get install git-core gnupg flex bison gperf libsdl1.2-dev libesd0-dev libwxgtk2.8-dev squashfs-tools build-essential zip curl libncurses5-dev zlib1g-dev pngcrush schedtool libxml2 libxml2-utils xsltproc g++-multilib lib32z1-dev lib32ncurses5-dev lib32readline-gplv2-dev gcc-multilib
y
You will now need to set up the directories for your build environment. Type this into the terminal:
Code:
mkdir -p ~/bin
mkdir -p ~/android/cm-10.2
Set up the repo binary (used for syncing your local repository with the CM source):
Code:
curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo
NOTE: In order to run the repo command when you're not in ~/bin (the folder where you saved the repo binary), you need to add it to your path of execution. To do this, type:
Code:
gedit ~/.bashrc
And then add the line
Code:
export PATH=${PATH}:~/bin
to the top of the file and click save. You can do the same for the adb and fastboot commands by adding
Code:
export PATH=${PATH}:~/android/sdk/adt-bundle/sdk/tools
export PATH=${PATH}:~/android/sdk/adt-bundle/sdk/platform-tools
to the file.
Click to expand...
Click to collapse
Syncing your local repository with the CM source
The next step is to initialize the repository and download the CM source code to your computer. Type the following lines into the terminal:
Code:
cd ~/android/cm-10.2
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2
repo sync
You have now begun downloading all of the CM source code to your build directory. Depending on your internet speed, this can take up to a couple of hours. If the sync interrupts, don't worry. Simply continue the sync (you don't have to restart completely, only the project you were downloading when the interrupt occured, phew) by entering:
Code:
repo sync
Remember, you need to cd into your build directory (~/android/cm-10.2, if you've been following this guide) for the command to work.
Go and get yourself a drink or something, this step takes a long time.
NOTE: If the sync gets stuck at 99%, stop the sync (exit the terminal window), open up a new one, cd to your build directory, and type the following:
Code:
repo sync -j1
This reduces the amount of threads/connections to 1 for the final unsynced project(s). It should work.
Click to expand...
Click to collapse
Now comes the fun part: Building
You're almost to the end! In order to make a working build, you have to get the proprietary files (mainly device build files and drivers) for the Nexus 4. The easiest way to do this is to create a file named "roomservice.xml" in the ~/android/cm-10.2/.repo/local_manifests directory. Now, .repo is a hidden directory, so in order to access that directory you can either 1) show hidden files and folders in Nautilus (the Ubuntu file manager) or 2) access the folder and create the file using terminal commands. Both methods are explained below (2 is probably easier, but does not always work, in my experience).
1) Open up a Nautilus window. Navigate to your build directory (once again, ~/android/cm-10.2) and press Ctrl+H. This allows you to see hidden files and folders. You should see a folder labelled .repo. Enter it and inside, create a directory called "local_manifests", if there isn't already one. Enter that folder and create a blank file called "roomservice.xml". Next, copy the following lines into the file and press save:
Code:
<manifest>
<project name="TheMuppets/proprietary_vendor_lge.git" path="vendor/lge" remote="github" revision="cm-10.2"/>
</manifest>
2) Type this into the terminal:
gedit ~/android/cm-10.2/.repo/local_manifests/roomservice.xml
ext, copy the following lines into the file and press save:
Code:
<manifest>
<project name="TheMuppets/proprietary_vendor_lge.git" path="vendor/lge" remote="github" revision="cm-10.2"/>
</manifest>
If you get an error, try method 1.
Do another repo sync:
Code:
repo sync
After this, you can download the necessary pre-built apps:
Code:
~/android/cm-10.2/vendor/cm/get-prebuilts
Finally, you will build. If you aren't there already, cd to your build directory and run the following commands in the terminal:
Code:
. build/envsetup.sh
brunch mako
Now, just let your computer do the rest. This step is very demanding for your computer, so I recommend you leave it alone while it builds. Go get another drink.
Done? If everything went correctly, cd to ~/android/cm-10.2/out/target/product/mako and you should see your newly built ROM entitled:
cm-10.2-20xxxxxx-UNOFFICIAL-mako.zip
Congratulations! You've successfully built CM 10.2!
For re-builds (i.e. when the source code has been updated and you would like to make a new nightly), just do this:
Code:
cd ~/android/cm-10.2
make clean [I](for incremental builds, you can skip this step. You can also do make clobber; thanks [user=4520802]@obtained[/user])[/I]
repo sync
. build/envsetup.sh
brunch mako
If you ever encounter an error or problem and need help, feel free to post here or send me a PM.
Happy building, everyone!
Sources:
How To Build CyanogenMod Android for Google Nexus 4 ("mako")
http://wiki.cyanogenmod.org/w/Build_for_mako
[GUIDE] How to build CM10.1 (Android 4.2.1) for the Nexus 4 (mako)
http://forum.xda-developers.com/showthread.php?t=2047981
[GUIDE] Building CM10.2 for Nexus 4 with Mac OS X 10.8.X)[UPDATED: 8.8.2013]
http://forum.xda-developers.com/showthread.php?t=2087318
UBUNTU 12.04 - INSTALL ANDROID TOOLS (ADB, FASTBOOT, ...)
http://bernaerts.dyndns.org/linux/245-ubuntu-precise-install-android-sdk
Reserved
Nice thanks for the guide muchly appreciated!
Sent from my Nexus 4 using Tapatalk 4
Other phones
Very nice guide, but i was wondering if this is working for other phones too? Which i think it does but i was kind of wondering about this part "Now comes the fun part: Building", i want to do this on samsung galaxy s2 (gt-i9100), will i write the same things (execpt from bunch mako)?
You missed the "repo sync" command after creating roomservice.xml file, it is necessary to download the device specific files. (sorry my english)
Cheerpipe said:
You missed the "repo sync" command after creating roomservice.xml file, it is necessary to download the device specific files. (sorry my english)
Click to expand...
Click to collapse
You are absolutely correct. Thanks for that
Sent by carrier pigeon
Chekhn said:
Very nice guide, but i was wondering if this is working for other phones too? Which i think it does but i was kind of wondering about this part "Now comes the fun part: Building", i want to do this on samsung galaxy s2 (gt-i9100), will i write the same things (execpt from bunch mako)?
Click to expand...
Click to collapse
You'd also need the correct proprietary (device-specific) files. I'm not sure that TheMuppets has the files for the i9100. You may need to extract them from a working build of CM yourself.
You can check out CM's guide for your device here: http://wiki.cyanogenmod.org/w/Build_for_i9100
Sent by carrier pigeon
klvnhng said:
You'd also need the correct proprietary (device-specific) files. I'm not sure that TheMuppets has the files for the i9100. You may need to extract them from a working build of CM yourself.
You can check out CM's guide for your device here: http://wiki.cyanogenmod.org/w/Build_for_i9100
Sent by carrier pigeon
Click to expand...
Click to collapse
I have checked the CM build guide, but i don't get the zip file when i do cd $OUT, have been searching but no answer and I can't find any threads or posts with this problem.
Chekhn said:
I have checked the CM build guide, but i don't get the zip file when i do cd $OUT, have been searching but no answer and I can't find any threads or posts with this problem.
Click to expand...
Click to collapse
You probably didn't get the device blobs correctly. I did a search for the i9100 and it turns out that TheMuppets repo does have it.
So for roomservice.xml:
Code:
<manifest>
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-10.2" />
</manifest>
And when building:
Code:
brunch i9100
klvnhng said:
You'd also need the correct proprietary (device-specific) files. I'm not sure that TheMuppets has the files for the i9100. You may need to extract them from a working build of CM yourself.
You can check out CM's guide for your device here: http://wiki.cyanogenmod.org/w/Build_for_i9100
Sent by carrier pigeon
Click to expand...
Click to collapse
TheMuppets does have i9100 proprietary files.
Edit: looks like I'm 1 minute late.
Also: make clobber and make clean are the same for cm. "make clobber" actually does a "make clean".
Sent from my Nexus 4 using xda premium
@klvnhng
Are you sure we can make this with Java 7?. I tried some days ago to build AOSP and some other ROM´s, and I had so much problems becasue of the Java version when building. I had Java 7, but specifically the build asked for Java 6, so I had to downgrade.
Another question would be if it is necessary to download the code for all the devices, instead of downloading the code just for Mako.
Thanks.
Galaxo60 said:
@klvnhng
Are you sure we can make this with Java 7?. I tried some days ago to build AOSP and some other ROM´s, and I had so much problems becasue of the Java version when building. I had Java 7, but specifically the build asked for Java 6, so I had to downgrade.
Another question would be if it is necessary to download the code for all the devices, instead of downloading the code just for Mako.
Thanks.
Click to expand...
Click to collapse
Hmm...you may be correct. I have both 6 and 7 installed, so it could be that I'm actually using 6.
Edit: JDK 6 is required (http://source.android.com/source/initializing.html). I have a mixed environment.
And yes, in order to build CM, you need to have the entire source repo synced. Sorry
Thank you for the help guys!
Excellent!
Great guide... Very thorough and informative. Getting ready to build my first 10.2 shortly... Thanks again
VoiD_Dweller said:
Great guide... Very thorough and informative. Getting ready to build my first 10.2 shortly... Thanks again
Click to expand...
Click to collapse
Let me know how it goes!
wow i needed this thread since 1 month i am trying but not able to build properly now u r here to help thnkx.
I will try ! Thx
Sent from my Nexus 4 using xda app-developers app
Noob's question ; what are the differences between a home compiled rom and the rom you can download on the CM website ?
klvnhng said:
Let me know how it goes!
Click to expand...
Click to collapse
Got the build done.. flashed it, flashed gapps, everything works excellent!
One thing though, I noticed the build size of the zip is 9 mb larger than the official nightly for yesterday. Whats up with that?
Also what are the perks of building on ubuntu 13.04 vs the recommended 12.04 I always see in the other guides? are the tools more optimized or something? I'm a linux newb so excuse me if it's a lame question
---------- Post added at 08:06 AM ---------- Previous post was at 08:05 AM ----------
french-anonymous said:
Noob's question ; what are the differences between a home compiled rom and the rom you can download on the CM website ?
Click to expand...
Click to collapse
You built it, and you don't have to wait for their build server. Also after you learn more about it, you can customize and add things of your own.. basically.
VoiD_Dweller said:
Got the build done.. flashed it, flashed gapps, everything works excellent!
One thing though, I noticed the build size of the zip is 9 mb larger than the official nightly for yesterday. Whats up with that?
Click to expand...
Click to collapse
To be honest, I'm not quite sure. My builds average 206 MB.
VoiD_Dweller said:
Also what are the perks of building on ubuntu 13.04 vs the recommended 12.04 I always see in the other guides? are the tools more optimized or something? I'm a linux newb so excuse me if it's a lame question
Click to expand...
Click to collapse
Apparently, the 3.8 kernel included in 13.04 handles tasks more efficiently. There are other optimizations as well, I'm sure. Most people recommend 12.04 because it is a LTS version and therefore will have bug fix and security updates for for 5 years, as opposed to 9 months. But I like to keep up-to-date :good:
I have started to build cm12 from sources
as I dont have high speed bandwidth I'm using this
http://forum.xda-developers.com/android/development/source-cyanogenmod-source-highly-t3069473
All thanks to te dev who created it
I'm stuck at
-> where should I give kernel sources path so that it syncs from github?
->I have written cm.mk and local_manifests/roomservice.xml - still not syncing
the error which I get ->
~/cm12/cm12 $ breakfast dior
including vendor/cm/vendorsetup.sh
ls: cannot access device/*/dior/cm.mk: No such file or directory
build/core/product_config.mk:234: *** Can not locate config makefile for product "cm_dior". Stop.
Device dior not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Repository for dior not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
ls: cannot access device/*/dior/cm.mk: No such file or directory
build/core/product_config.mk:234: *** Can not locate config makefile for product "cm_dior". Stop.
** Don't have a product spec for: 'cm_dior'
** Do you have the right repo manifest?
this is help for u guys also @sm_94 and @BennyBron
mentions -> @stane1983 @haoyangw please help us :highfive:
Create a local_manifest folder inside the .repo folder. Then create a local_manifest.xml and then add all your device specific repos like shown below. Sync again and use "brunch dior" without quotes to build.
I have used Stane1983's repos as an example. Use the ones you need.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/xiaomi/dior" name="Stane1983/android_device_xiaomi_dior" remote="github" revision="cm-12.0_new" />
<project path="kernel/xiaomi/dior" name="Stane1983/android_kernel_xiaomi_dior" remote="github" revision="cm-12.0" />
<project path="vendor/xiaomi/dior" name="Stane1983/android_vendor_xiaomi_dior" remote="github" revision="cm-12.0_new" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-12.0" />
<project name="CyanogenMod/android_hardware_qcom_fm" path="hardware/qcom/fm" remote="github" revision="cm-12.0" />
</manifest>
Thank you, 1 more question
Silesh.Nair said:
Create a local_manifest folder inside the .repo folder. Then create a local_manifest.xml and then add all your device specific repos like shown below. Sync again and use "brunch dior" without quotes to build.
I have used Stane1983's repos as an example. Use the ones you need.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/xiaomi/dior" name="Stane1983/android_device_xiaomi_dior" remote="github" revision="cm-12.0_new" />
<project path="kernel/xiaomi/dior" name="Stane1983/android_kernel_xiaomi_dior" remote="github" revision="cm-12.0" />
<project path="vendor/xiaomi/dior" name="Stane1983/android_vendor_xiaomi_dior" remote="github" revision="cm-12.0_new" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-12.0" />
<project name="CyanogenMod/android_hardware_qcom_fm" path="hardware/qcom/fm" remote="github" revision="cm-12.0" />
</manifest>
Click to expand...
Click to collapse
Thank you for the help, I will try it now!
can u help me use this http://forum.xda-developers.com/android/development/compressed-compressed-android-sources-t3051687
as I dont have super speed internet to download the huge sources I have to use this compressed sources, Please help me use this, and do i need the repo folder as mentioned in that thread or just the sources zip?
Thanks again! and by the way, do u own this device and interested in its development? we have some serious bug like camera we could use some Pro devs help
Pavan l said:
Thank you for the help, I will try it now!
can u help me use this http://forum.xda-developers.com/android/development/compressed-compressed-android-sources-t3051687
as I dont have super speed internet to download the huge sources I have to use this compressed sources, Please help me use this, and do i need the repo folder as mentioned in that thread or just the sources zip?
Thanks again! and by the way, do u own this device and interested in its development? we have some serious bug like camera we could use some Pro devs help
Click to expand...
Click to collapse
I don't suggest you use that. What's your internet speed like? Try syncing one repo at a time ( repo sync -j1 ). You can also remove many repos that you don't need for compiling thereby saving bandwidth.
I have ordered the device and should get it by monday. In the meantime, I am compiling a temasek cm-12.0 build. If anyone is willing to test it, I will post links when its done. I am no dev btw.
Silesh.Nair said:
I don't suggest you use that. What's your internet speed like? Try syncing one repo at a time ( repo sync -j1 ). You can also remove many repos that you don't need for compiling thereby saving bandwidth.
I have ordered the device and should get it by monday. In the meantime, I am compiling a temasek cm-12.0 build. If anyone is willing to test it, I will post links when its done. I am no dev btw.
Click to expand...
Click to collapse
I am willing to test!
thank you
Silesh.Nair said:
I don't suggest you use that. What's your internet speed like? Try syncing one repo at a time ( repo sync -j1 ). You can also remove many repos that you don't need for compiling thereby saving bandwidth.
I have ordered the device and should get it by monday. In the meantime, I am compiling a temasek cm-12.0 build. If anyone is willing to test it, I will post links when its done. I am no dev btw.
Click to expand...
Click to collapse
My internet speed is 4mbps, where download speed is about 512kbps till 20GB only, after that download speed decreases to 65kbps and this resets every month... So I'm not able to sync huge 30GB sources :crying:
And yeah we have many testers!! Feel free to post ur rom!!
It's not 30gb, it's around 20gb but it's worth of dloading
Sent from my HM NOTE 1LTE using Tapatalk
No working camera!!!
{
"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"
}
Sent from my Xiaomi Note 4G using Tapatalk
☺
Oow awesome man...
Silesh.Nair said:
No working camera!!!
Sent from my Xiaomi Note 4G using Tapatalk
Click to expand...
Click to collapse
Have you built it or its just stane's one?
Sent from my HM NOTE 1LTE using Tapatalk
Check the date. I built it and fixed a few issues like button lights and battery charging.
OOPs!!! uploaded the wrong screenie. Here you go.
Congratulations, upload ur github with changes if you can. Tnx
Sent from my HM NOTE 1LTE using Tapatalk
sm_94 said:
Congratulations, upload ur github with changes if you can. Tnx
Sent from my HM NOTE 1LTE using Tapatalk
Click to expand...
Click to collapse
github.com/sileshn
Can you logcat time when u open camera app and it crashes, and upload it to pastebin then here?
Sent from my HM NOTE 1LTE using Tapatalk
sm_94 said:
Can you logcat time when u open camera app and it crashes, and upload it to pastebin then here?
Sent from my HM NOTE 1LTE using Tapatalk
Click to expand...
Click to collapse
I am looking at it. Some vendor blobs are missing. I will make another build tomorrow with some added blobs and a few changes. Will post the logcat then.
Will upload tomorrow's build.
---------- Post added at 03:26 PM ---------- Previous post was at 03:25 PM ----------
daviduco said:
Share build pls.
Post what's working and what isn't, or create a new thread...
Click to expand...
Click to collapse
No hardware acceleration, no camera. Rest seem ok as of now.
this is soooo crazy haha. Keep up the goodwork. care to test headphones and its loudness?
OldYellowBricks said:
this is soooo crazy haha. Keep up the goodwork. care to test headphones and its loudness?
Click to expand...
Click to collapse
Headphones are OK for me, but its subjective. Differs from person to person.
Did u mean too loud or low sound?
Sent from my Xiaomi Note 4G using Tapatalk
Silesh.Nair said:
Headphones are OK for me, but its subjective. Differs from person to person.
Did u mean too loud or low sound?
Sent from my Xiaomi Note 4G using Tapatalk
Click to expand...
Click to collapse
For me its kinda low, but on stock rom i did a workaround by tweaking the mixer_path file :good:
As long as theres audio then its okay
OldYellowBricks said:
For me its kinda low, but on stock rom i did a workaround by tweaking the mixer_path file :good:
As long as theres audio then its okay
Click to expand...
Click to collapse
Can you tell how to increase sound in miui 6
finally,some more active people working on note....will be glad for help in anything..