Database Users

CM10 JB Rom boot loop..

Anyone have experienced boot loop for the CM10 build?

wagnus said:
Anyone have experienced boot loop for the CM10 build?
Click to expand...
Click to collapse
Anyway this ROM is so fast and great and I really would like to flash it for daily use! :good:

Many issues with video playback as well as some audio problems, it may be fast but if video does not work then what is the point. I am waiting on a response as how to convert videos in order to play them back using CM10.
Sent from my GT-P6800 using xda premium

adinis78 said:
Many issues with video playblack as some audio problems, it may be fast but if video does not work then what is the point. I am waiting on a response as how to convert videos in order to play them back using CM10.
Sent from my GT-P6800 using xda premium
Click to expand...
Click to collapse
I have reflashed this ROM again from stock HC, full data/cache wipe. Everything's seems smooth currently..

Setup a standard CyanogenMod 10 build environment (there are plenty of tutorials on the web already on how to do this). Then
Add add the following entries to your local manifest
Code:
<project path="device/samsung/XXX"
name="ohanar/android_device_samsung_XXX"
revision="jellybean"
remote="github" />
<project path="device/samsung/smdk4210-tab"
name="ohanar/android_device_samsung_smdk4210-tab"
revision="jellybean"
remote="github" />
<project path="kernel/samsung/smdk4210-tab"
name="ohanar/android_kernel_samsung_smdk4210-tab"
revision="ics"
remote="github" />
where you replace XXX with your device (i815, p6200, p6210, p6800, p6810, or t869).
Make sure that your device is running the newest build of CyanogenMod 10.
Make sure your device is plugged in and has debugging enabled.
Run the extract-files script from your particular device tree.
Run vendor/cm/get-prebuilts
Your sources are now ready, to build run
Code:
$ . build/envsetup.sh # this sets up the build environment
$ lunch cm_XXX-userdebug # this selects your device
$ mka bacon # this builds CM
Click to expand...
Click to collapse
Any know how to configure the local manifest ? I've been googled for this but still unable to understand..

wagnus said:
Any know how to configure the local manifest ? I've been googled for this but still unable to understand..
Click to expand...
Click to collapse
Copy and Paste the xml to
/path/to/your/build/directory/.repo/local_manifest.xml
e.g. /home/username/android/system/.repo/local_manifest.xml​
And beware of the typo, its make bacon​ not mka bacon​

lowtraxx said:
Copy and Paste the xml to
/path/to/your/build/directory/.repo/local_manifest.xml
e.g. /home/username/android/system/.repo/local_manifest.xml​
And beware of the typo, its make bacon​ not mka bacon​
Click to expand...
Click to collapse
Thanks a million! At least now I got some clues..:good:

Please I reflashed my p6800 to Stock HC and now it asks me for a password , Any clues what the password is ???

mayaco said:
Any clues what the password is ???
Click to expand...
Click to collapse
Try this: http://forum.xda-developers.com/showpost.php?p=12453585&postcount=1332
Keep us posted

Now Im On galaxy tab 7.7 screen and hanged in there , Tried to flash stock HC again , same issue , Tried to slash Stock ICS, same stucked galaxy tab 7.7 sceen nthng further , >>>>>> Wt shall i do now pleaseeeeeeeeeeeee?????
---------- Post added at 11:11 AM ---------- Previous post was at 10:49 AM ----------
Astrix Ashburn said:
Try this: http://forum.xda-developers.com/showpost.php?p=12453585&postcount=1332
Keep us posted
Click to expand...
Click to collapse
I did bt Im still on the same password query screen (asking me to enter your password ?)
thanx alot though for ur efforts:good:

Build Instructions for Ubuntu

Thanks to mamenyaka's efforts, we now have a running version of Ubuntu Touch on the Xperia Tablet Z. I'm attempting to do some customization of this kernel (such as add btusb support), but I'm not all the familiar with the Cyanogen build process. So looking for a little help here.
I've been following these instructions:
http://wiki.cyanogenmod.org/w/Build_for_pollux_windy
Now, I think the process is as follows:
Setup environment according to the wiki, up through the "repo init" step.
Add the "local_manifest.xml" from https://github.com/mamenyaka/android/ to ~/android/system/.repo/local_manifests
Run a repo sync in ~/android/system.
and this is where I get a bit confused. I _think_ the next step is then to run source build/envsetup.sh and breakfast pollux_windy, and then proceed according to the instructions as usual, excepting extracting the blobs. I think those are already included.
However, can someone confirm this? Or is there a step/steps I'm leaving out?
Thanks.
PS - yes, this should probably be in the dev forum, but the post count rules are forcing me to post it here...

If you want to build Ubuntu Touch, you should follow the porting guide.
You can't mix the two. The CM repo init and ubuntu's phablet-dev-bootstrap (ubuntu's repo init) use very different manifest.xmls. And if you want to build CM (advised if you never built android from source), you don't need the repos from my github.
Next thing: breakfast. It is a good to use when you build CM, but it's not good for building Ubuntu Touch. Breakfast adds CM repos specific to your device in a file in .repo/local_manifest (roomservice.xml). For Ubuntu Touch you don't need all of the device specific repos and you also need to apply some modifications in these repos (which I already done), and to use them, you will need to add the repos manually (local_manifest/local_manifest.xml, similar to roomservice.xml, but I prefer this file, because roomservice.xml is related to breakfast), so no breakfast needed.
Then simply repo sync to get the new repos.
The extra blobs are included thanks to TheMuppets repos.
To start building, simply $ . build/envsetup.sh and $ brunch pollux_windy. But all of this can be found in the guide or on CM wiki.
For building Ubuntu Touch you need a few extra things mentioned in the guide, like the phablet tool, and you need to update the ubuntu/platform-api bzr repo (bzr pull) - this isn't done by repo sync because it isn't a git repo, it's ubuntu's bazaar.

mamenyaka said:
If you want to build Ubuntu Touch, you should follow the porting guide.
You can't mix the two. The CM repo init and ubuntu's phablet-dev-bootstrap (ubuntu's repo init) use very different manifest.xmls. And if you want to build CM (advised if you never built android from source), you don't need the repos from my github.
Next thing: breakfast. It is a good to use when you build CM, but it's not good for building Ubuntu Touch. Breakfast adds CM repos specific to your device in a file in .repo/local_manifest (roomservice.xml). For Ubuntu Touch you don't need all of the device specific repos and you also need to apply some modifications in these repos (which I already done), and to use them, you will need to add the repos manually (local_manifest/local_manifest.xml, similar to roomservice.xml, but I prefer this file, because roomservice.xml is related to breakfast), so no breakfast needed.
Then simply repo sync to get the new repos.
The extra blobs are included thanks to TheMuppets repos.
To start building, simply $ . build/envsetup.sh and $ brunch pollux_windy. But all of this can be found in the guide or on CM wiki.
For building Ubuntu Touch you need a few extra things mentioned in the guide, like the phablet tool, and you need to update the ubuntu/platform-api bzr repo (bzr pull) - this isn't done by repo sync because it isn't a git repo, it's ubuntu's bazaar.
Click to expand...
Click to collapse
Okay, thanks for pointing me in the right direction. Thought I had to use CM build instead to use your repos. That's why this thread is here. I'd like to get instructions out here that could decrease the learning curve on some of this.
Are you aware of the state of CM on pollux_windy? I notice that Ubuntu has breakfast in their official porting guide now. Would you expect that to work, or are there further changes in your repositories to enhance their work?
In other words, Ubuntu's guide suggests doing a "breakfast pollux_windy", "repo sync", some tweaks, and then a build, under the Automatic build section.
I think your repo would work with the process under the "Manual (deprecated)" section. Is there a reason to use one over the other? Have you already integrated the required modifications in your repos, for example?
Sorry if this is all a bit pedantic. Just trying to come up to speed on the build process for all of this. I've built many a linux kernel, but I'm not at all familiar with this build process.
Thanks again for your help.

themikem said:
Okay, thanks for pointing me in the right direction. Thought I had to use CM build instead to use your repos. That's why this thread is here. I'd like to get instructions out here that could decrease the learning curve on some of this.
Are you aware of the state of CM on pollux_windy? I notice that Ubuntu has breakfast in their official porting guide now. Would you expect that to work, or are there further changes in your repositories to enhance their work?
In other words, Ubuntu's guide suggests doing a "breakfast pollux_windy", "repo sync", some tweaks, and then a build, under the Automatic build section.
I think your repo would work with the process under the "Manual (deprecated)" section. Is there a reason to use one over the other? Have you already integrated the required modifications in your repos, for example?
Sorry if this is all a bit pedantic. Just trying to come up to speed on the build process for all of this. I've built many a linux kernel, but I'm not at all familiar with this build process.
Thanks again for your help.
Click to expand...
Click to collapse
Don't worry, I am here to answer your questions.
So, breakfast in Ubuntu Touch is good when you want to start off a brand new port.
The advantage of using my repos and using the manual method is that I already integrated the required modifications and, most importatnly, the image builds. Simply using the CM repos, you would get build errors, which are fixed in my repos; for example, removing the android parts.
Also, if you are interested, you could join this group.

mamenyaka said:
Don't worry, I am here to answer your questions.
So, breakfast in Ubuntu Touch is good when you want to start off a brand new port.
The advantage of using my repos and using the manual method is that I already integrated the required modifications and, most importatnly, the image builds. Simply using the CM repos, you would get build errors, which are fixed in my repos; for example, removing the android parts.
Also, if you are interested, you could join this group.
Click to expand...
Click to collapse
Thanks for the tip. It worked!
For the record, it turned out to be this simple:
(~/phablet is arbitrary)
mkdir ~/phablet && cd ~/phablet
phablet-dev-bootstrap ~/phablet
repo sync
Add ~/phablet/.repo/local_manifests/local_manifest.xml from: https://github.com/mamenyaka/android
repo sync
. build/envsetup.sh
brunch pollux_windy
...and then flash the files from $OUT (~/android/system/out/target/product/pollux_windy)
Also note that I had a terrible time making git work through my NAT. Tried both a hardware router (Cisco) and my standard Vyatta VM. Ultimately had to put my build machine directly on a publicly-routable IP to make it go. If you're having problems with Git on 13.04, it could be the same issue. I'm not aware of any other fix, other than finding some way to switch the build system to http:// instead of git://
Now off to reconfigure the kernel. This should be interesting...

One thing, without this you won't be able too boot.
You need to replace boot.img from the .zip with ubuntu-boot.img from $OUT and rename, of course, to boot.img.
ubuntu-boot.img should be bigger in size.

Hope this is the right place, but am I correct to assume that its possible to run Ubuntu Touch on the Xperia Z Tablet?
If so are there any tutorials on this?
Tel'X

telx85 said:
Hope this is the right place, but am I correct to assume that its possible to run Ubuntu Touch on the Xperia Z Tablet?
If so are there any tutorials on this?
Tel'X
Click to expand...
Click to collapse
You gotta be kidding, right?
http://forum.xda-developers.com/showthread.php?t=2336018

mamenyaka said:
You gotta be kidding, right?
http://forum.xda-developers.com/showthread.php?t=2336018
Click to expand...
Click to collapse
Nope, but thanks for that.
Looks very promising.

mamenyaka said:
Don't worry, I am here to answer your questions.
So, breakfast in Ubuntu Touch is good when you want to start off a brand new port.
The advantage of using my repos and using the manual method is that I already integrated the required modifications and, most importatnly, the image builds. Simply using the CM repos, you would get build errors, which are fixed in my repos; for example, removing the android parts.
Also, if you are interested, you could join this group.
Click to expand...
Click to collapse
I have some questions, for example I want to try build the ubuntu touch to a new port (actually not new port, just the progress of development of my phone is held on), I just refer to your local manifest.xml file? Sure I know need to change to device specific repo, I have it on other developer github.
Just the question is, how do I recognise which part is belong to android parts and remove them? Or which part should be remained?
Sent from my SGP311 using xda app-developers app

Trevor Chuah said:
I have some questions, for example I want to try build the ubuntu touch to a new port (actually not new port, just the progress of development of my phone is held on), I just refer to your local manifest.xml file? Sure I know need to change to device specific repo, I have it on other developer github.
Just the question is, how do I recognise which part is belong to android parts and remove them? Or which part should be remained?
Sent from my SGP311 using xda app-developers app
Click to expand...
Click to collapse
You have a cm.dependencies file in your device's repo which tells what other repos it needs (for example kernel).
You can instantly remove any android app related repo (like android_packages_apps_FMRadio).
But if you tell me what phone, I can give you some hints.

mamenyaka said:
You have a cm.dependencies file in your device's repo which tells what other repos it needs (for example kernel).
You can instantly remove any android app related repo (like android_packages_apps_FMRadio).
But if you tell me what phone, I can give you some hints.
Click to expand...
Click to collapse
The phone I'm using is Xperia S. The developer has his github name OpenSEMC.
Thank you.
Sent from my Xperia S using xda app-developers app

Trevor Chuah said:
The phone I'm using is Xperia S. The developer has his github name OpenSEMC.
Thank you.
Sent from my Xperia S using xda app-developers app
Click to expand...
Click to collapse
You could start over from scratch. Just fork the CM repos. The OpenSEMC repos are not really ubuntu touch oriented.

mamenyaka said:
You could start over from scratch. Just fork the CM repos. The OpenSEMC repos are not really ubuntu touch oriented.
Click to expand...
Click to collapse
Okay. So basically the post #5 is applicable to every phone right?
I just follow it and modify the
1) local manifest to correct repo
2) remove the android part
Right?
I will try it.
Thank you.
Sent from my Xperia S using xda app-developers app

May I ask?
If I use phablet-dev-bootstrap, it will follow the android.git in http://phablet.ubuntu.com/gitweb right?
I did it, and
I checked the default.xml inside the android repo, to roughly compare with the file synced into local.
I found that it has many thing missing, for example the following:
Code:
<project path="external/mockwebserver" name="CyanogenMod/android_external_mockwebserver" />
<project path="external/mp4parser" name="CyanogenMod/android_external_mp4parser" />
<project path="frameworks/opt/inputmethodcommon" name="CyanogenMod/android_frameworks_opt_inputmethodcommon" />
<project path="frameworks/opt/mailcommon" name="CyanogenMod/android_frameworks_opt_mailcommon" />
and many of them.
Is it ubuntu automatically not download these file since they are not important?

Trevor Chuah said:
May I ask?
If I use phablet-dev-bootstrap, it will follow the android.git in http://phablet.ubuntu.com/gitweb right?
I did it, and
I checked the default.xml inside the android repo, to roughly compare with the file synced into local.
I found that it has many thing missing, for example the following:
Code:
<project path="external/mockwebserver" name="CyanogenMod/android_external_mockwebserver" />
<project path="external/mp4parser" name="CyanogenMod/android_external_mp4parser" />
<project path="frameworks/opt/inputmethodcommon" name="CyanogenMod/android_frameworks_opt_inputmethodcommon" />
<project path="frameworks/opt/mailcommon" name="CyanogenMod/android_frameworks_opt_mailcommon" />
and many of them.
Is it ubuntu automatically not download these file since they are not important?
Click to expand...
Click to collapse
Be sure to check out the phablet-saucy branch of default.xml, that's what phablet-dev-bootstrap pulls.
---------- Post added at 11:40 AM ---------- Previous post was at 11:30 AM ----------
Trevor Chuah said:
Okay. So basically the post #5 is applicable to every phone right?
I just follow it and modify the
1) local manifest to correct repo
2) remove the android part
Right?
I will try it.
Thank you.
Sent from my Xperia S using xda app-developers app
Click to expand...
Click to collapse
Mostly right, but there is always something extra that needs to be done with every device.
Be sure to get the sony proprietary blobs from TheMuppets on github and post any questions, errors you need help with.

mamenyaka said:
Be sure to check out the phablet-saucy branch of default.xml, that's what phablet-dev-bootstrap pulls.
---------- Post added at 11:40 AM ---------- Previous post was at 11:30 AM ----------
Mostly right, but there is always something extra that needs to be done with every device.
Be sure to get the sony proprietary blobs from TheMuppets on github and post any questions, errors you need help with.
Click to expand...
Click to collapse
The following is my local_manifest.xml file
Code:
<project path="device/sony/common" name="OpenSEMC/android_device_sony_common" remote="github" revision="cm-10.1" />
<project path="device/sony/nozomi" name="OpenSEMC/android_device_sony_nozomi" remote="github" revision="cm-10.1" />
<project path="device/sony/fuji-common" name="OpenSEMC/android_device_sony_fuji-common" remote="github" revision="cm-10.1" />
<project path="device/sony/qcom-common" name="OpenSEMC/android_device_sony_qcom-common" remote="github" revision="cm-10.1-legacy" />
<project path="kernel/sony/msm8x60" name="OpenSEMC/android_kernel_sony_msm8x60" remote="github" revision="cm-10.1-legacy" />
<project path="vendor/sony" name="OpenSEMC/proprietary_vendor_sony" remote="github" revision="cm-10.1-lagacy" />
<project path="hardware/sony/DASH" name="OpenSEMC/android_hardware_sony_DASH" remote="github" revision="cm-10.1" />
<project path="hardware/qcom/media" name="OpenSEMC/android_hardware_qcom_media-legacy" remote="github" revision="cm-10.1-legacy" />
I referred to your local_minifest.xml and the original author xml file and conclude this.
I do not know is it correct or not.
May I ask, will the recovery automatically add into the compile device image? What will it use? CWM?

Trevor Chuah said:
The following is my local_manifest.xml file
I referred to your local_minifest.xml and the original author xml file and conclude this.
I do not know is it correct or not.
May I ask, will the recovery automatically add into the compile device image? What will it use? CWM?
Click to expand...
Click to collapse
I think you should go with CyanogenMod for all repos except vendor, and TheMuppets for the vendor/sony (revision=cm-10.1 for all) if you want to start clean. Then just follow the porting guide.
It will use CWM.

mamenyaka said:
I think you should go with CyanogenMod for all repos except vendor, and TheMuppets for the vendor/sony (revision=cm-10.1 for all) if you want to start clean. Then just follow the porting guide.
It will use CWM.
Click to expand...
Click to collapse
But CyanogenMod (FXP) did not publish CM10.1 for Xperia S, heard that they do not fix for the display.
Therefore I do not know whether if use the CM repo, what should I modify for the video to display.
Still newbie...

Trevor Chuah said:
But CyanogenMod (FXP) did not publish CM10.1 for Xperia S, heard that they do not fix for the display.
Therefore I do not know whether if use the CM repo, what should I modify for the video to display.
Still newbie...
Click to expand...
Click to collapse
I don't know much about nozomi. There exists the CM 10.1 repo for nozomi, but true, there is no cm-10.1 release.
You might have to experiment a little, stuff like common, qcom, DASH are available in CM, but if they have device specific fixes, than it may be the only route to use OpenSEMC repos.

[ROM][4.3][P7300/P7310][UNOFFICIAL] AOKP [2013-Sep-16]

WARNING: This is an experimental build!
Usual disclaimers:
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What's working:
WLAN
What's broken:
HDMI output
Untested:
Everything else
Please report device specific issues here: http://code.google.com/p/tab89cm/issues/list
All credits go to pershoot, AAccount, epinter and the AOKP team who did most of the work.
Downloads:
GApps (2013-Aug-24):
http://www.mediafire.com/download/yka61uuw7g90s70/gapps-jb-mr2-noneon-20130824-signed.zip, credits to dreamcwli
AOKP:
https://code.google.com/p/tab89cm/downloads/list?q=AOKP+4.3

Sources:
https://github.com/AOKP
https://github.com/pershoot
https://github.com/cmorlok
Init AOKP tree:
Code:
$ repo init -u https://github.com/AOKP/platform_manifest.git -b jb-mr2
My local_manifest.xml:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="github"
fetch="https://github.com/" />
<project name="cmorlok/android_kernel_samsung_p5" path="kernel/samsung/p5" remote="github" revision="refs/heads/cm-10.2" />
<project name="cmorlok/android_device_samsung_p4-common" path="device/samsung/p4-common" remote="github" revision="refs/heads/aokp-jb-mr2" />
<project name="cmorlok/android_device_samsung_p5" path="device/samsung/p5" remote="github" revision="refs/heads/aokp-jb-mr2" />
<project name="cmorlok/android_device_samsung_p5wifi" path="device/samsung/p5wifi" remote="github" revision="refs/heads/aokp-jb-mr2" />
<project name="cmorlok/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="refs/heads/cm-10.2" />
<remove-project name="AOKP/vendor_aokp"/>
<project name="cmorlok/vendor_aokp" path="vendor/aokp" remote="github" revision="refs/heads/jb-mr2" />
<remove-project name="AOKP/build" />
<project name="cmorlok/cm_android_build" path="build" remote="github" revision="refs/heads/aokp-jb-mr2" />
</manifest>

Oh my. Such a good dev never stops working. Thanks
Gửi từ Nokia chạy iOS

Awesome!!!
Sent from my I9105P using Xda Premium 4

The main reason I tried this is because AOKP allows to switch to the old tablet UI without breaking the new notification panel. I hope you guys will test that stuff. I'll post a poll later to find out which ROM (CM10.1/10.2/AOKP) is the most desired. I don't have much time at the moment and I don't use my tab at all (only on vacances ), so I would like to concentrate on one ROM.

@C-o-M: Will test this later today! Thanx!
Edit: Had to try it right away, and it is smoother than the CM-versions. Big thanks.

I will try when im at home thanks
Sent from my I9105P using Xda Premium 4

Can't force portrait mode no matter what I try. System settings or launcher settings.
Edit: lol, rotation option in system bar.
Sent from my GT-P7310 using xda app-developers app

Idlekilla said:
Edit: Had to try it right away, and it is smoother than the CM-versions. Big thanks.
Click to expand...
Click to collapse
Smoother than CM10.1 or CM10.2? CM10.1 is in my opinion very smooth whereas CM10.2 is kind of laggy.
@C-o-M: Will there also be a P7300 build, what I could test? Thanks!

Typing from AOKP now it is awesome
Sent from my GT-P7310 using xda app-developers app

I've installed the ROM today, I works fine,looks smooth ,at the touch / Browser I see now lags
I've flashed over cm10.2, with all wipes/ factory reset
What works:
WiFi
Bluetooth
Camera both
Root after installing su app
Multi user and profile doesn't work , it was working on the last cm10.2
Reboot,and reboot into recovery doesn't works
Edit1 Screenshot doesn't work
GPS untested ,I will try it later
Edit 2:
GPS doesn't work
Tab crashed when I put in the keyboard dock
Sent from my GT-P7310 using xda app-developers app

shiko80 said:
Smoother than CM10.1 or CM10.2? CM10.1 is in my opinion very smooth whereas CM10.2 is kind of laggy.
@C-o-M: Will there also be a P7300 build, what I could test? Thanks!
Click to expand...
Click to collapse
Smoother than anything I've tried. And that without overclocking to the usual 1400 MHz.
Sent from my GT-P7310 using xda app-developers app

Keynoard dock not working tablet crashes when you put him in the dock i have this problem also on cm10.2
Sent from my I9105P using Xda Premium 4

Smooth Rom, I like it
Roms runs very nice. Smoother than CM10.2, indeed. No idea about the battery yet, too short to tell.
Am unable to reboot though, either normal or to recovery. The tab will hang at a black screen. Only solution is to long-press power, all is well after that. Already reflashed a stock Rom using Odin, tried some different CWM versions, all with no avail.
Really odd. Anybody has any idea why this is, or even better, how to solve it? Starting from a clean slate (already did this several times now) right now is doable as I haven't fully configured the tab yet. :good:

I tried to do a dirty flash from cm10.2, but just sits on the splash screen doing its fancy animation (about 2hrs now). Guess I'll have to try find some time to factory reset...

Brendo said:
I tried to do a dirty flash from cm10.2, but just sits on the splash screen doing its fancy animation (about 2hrs now). Guess I'll have to try find some time to factory reset...
Click to expand...
Click to collapse
A dirty flash between different ROMs always fails. The problem is in most cases the format of the SQLite dbs used to store system data. Many ROMs (and each new version) add additional stuff, giving the DB a new version. You will most probably see a lot of "version mismatch" errors when you start an adb logcat during the fancy boot animation.
(You can of course take a deeper look on which DBs are wrong and delete them manually from /data. This would just delete the data from affected apps. But it isn't recommended at all. Better is to start from scratch and restore app data only from apps where you really need it)

safariking said:
Keynoard dock not working tablet crashes when you put him in the dock i have this problem also on cm10.2
Sent from my I9105P using Xda Premium 4
Click to expand...
Click to collapse
Dock without keyboard (only audio) freezes the tablet too.

No problem with GPS here. Flashed over CM 10.2 HD (safarikings) with all wipes and format system.

Hello Com
now I'm testing this ROM 3 days, depent off all issues, I'm going back to the last version of cm 10.2 from you.
This ROM is smooth , I see no lags, but cm 10.2 works for me better, when we can one version what have all functions from both where are the best, but I think this is not possible
Sent from my GT-P7310 using xda app-developers app

Swapped to AOKP from 10.2 a couple of days ago. Can't say I notice any performance difference myself. Happy with either on my P7310.
Maybe there are some differences I just haven't discovered?!
Nice to know which ROM will be kept in development, though.

[Q] Blank screen after flashing self compiled OMNI ROM

Anyone else experienced this? I'm building for Mako and the build is successful although after flashing the screen is just black after the google logo.
Do I need to extract the N4 binaries for this or am I missing something else? Thanks!
Sent from my Nexus 4 using XDA Premium 4 mobile app

You don't have the proprietary blobs.
Put the following line into your /omni/.repo/local_manifests/whatever.xml, resync and do a clobber recompile.
Code:
<project name="TheMuppets/proprietary_vendor_lge.git" path="vendor/lge" remote="github" revision="cm-10.2" />

chasmodo said:
You don't have the proprietary blobs.
Put the following line into your /omni/.repo/local_manifests/whatever.xml, resync and do a clobber recompile.
Code:
<project name="TheMuppets/proprietary_vendor_lge.git" path="vendor/lge" remote="github" revision="cm-10.2" />
Click to expand...
Click to collapse
Warning: This isn't guaranteed for all devices, as for some we're probably going to be diverging from current blob repos over time.
That is admittedly a bit of a problem now - without nightlies or existing builds, extract-files isn't the most reliable, and right now the blob repos the developers are using are private until we can sort out how to handle them. (Blob repos are always a bit of a complex legal grey area, which is why none of the official CM documentation references the repos at TheMuppets anywhere.)
For nearly all devices where it's known that SOMEONE has it booting from the repos you're using, blank screen on boot usually means no blobs. (A good way to check is to see if your ZIP is much smaller than typical for builds for that device.)

@Entropy512
and as non dev its imbossible to get hands on your private blobs atm?

In the mako build it mentions getting the blob files from developers.google.com/android/nexus/drivers#makojwr66y and putting them in the correct vendor directory. Should this work or is it necessary that we use the muppets binaries still?

Never mind, I figured out what the problem was thanks to some help in the irc chat. I updated the wiki page for building mako too.

caspian154 said:
Never mind, I figured out what the problem was thanks to some help in the irc chat. I updated the wiki page for building mako too.
Click to expand...
Click to collapse
What was the problem? Cause I have the same problem when trying to build rom for HTC One S C2.

makkeonmies said:
@Entropy512
and as non dev its imbossible to get hands on your private blobs atm?
Click to expand...
Click to collapse
It's quite possible - Quite a few people found them within 5 minutes of the first push to those repos on github...
The repos are public, we just don't go out of our way to point to them for various reasons.
(blob handling has always been a mess and will always suck - keep in mind that blob handling was one of the primary contributors to JBQ's final burnout and departure from AOSP.)

I built a cm13 rom but stuck at boot logo

I am new to android rom development.
My rom is using Altaf-Mahdi's source code.
There are no any errors while compiling.
After I flashed the rom and reboot, my phone stuck at boot logo almost 15 mins.
But it can boot recovery or fastboot
Is there any way to fix or get some logs?
Here is the flashable zip.
https://drive.google.com/file/d/0B_b1LHjDUqHjUUpmVmhXZDZ6Zmc/view?usp=sharing

ayackmk said:
I am new to android rom development.
My rom is using Altaf-Mahdi's source code.
There are no any errors while compiling.
After I flashed the rom and reboot, my phone stuck at boot logo almost 15 mins.
But it can boot recovery or fastboot
Is there any way to fix or get some logs?
Here is the flashable zip.
https://drive.google.com/file/d/0B_b1LHjDUqHjUUpmVmhXZDZ6Zmc/view?usp=sharing
Click to expand...
Click to collapse
Read this, you might get a hint.
http://forum.xda-developers.com/oneplus-2/general/cyanogenmod-13-android-marshmallow-t3256275

ahahahahahah not booting huh? did you add to the build this https://github.com/CyanogenMod/android_external_sony_boringssl-compat
and this https://github.com/CyanogenMod/android_external_stlport
???

manups4e said:
ahahahahahah not booting huh? did you add to the build this https://github.com/CyanogenMod/android_external_sony_boringssl-compat
and this https://github.com/CyanogenMod/android_external_stlport
???
Click to expand...
Click to collapse
Hail! :good::cyclops:

manups4e said:
ahahahahahah not booting huh? did you add to the build this [/url]https://github.com/CyanogenMod/android_external_sony_boringssl-compat[/url]
and this [/url]https://github.com/CyanogenMod/android_external_stlport[/url]
???
Click to expand...
Click to collapse
Thank s:laugh:
I have this
<project path="external/boringssl" name="CyanogenMod/android_external_boringssl" groups="pdk" />
but no android_external_stlport
is it necessary?
What is these for?
Sorry I am really new to android rom development and bad English:highfive:
((But I tried to flash boot,system,userdata in fastboot directly, It can boot.

ok so.. boringssl-compat is a must if you want to build with lollipop blobs.
external_stlport is needed to build libs for qualcomm devices.
this is what you need to put into your local_manifest.xml
Code:
<project path="external/sony/boringssl-compat" name="CyanogenMod/android_external_sony_boringssl-compat" remote="github" revision="cm-13.0" />
<project path="external/stlport" name="CyanogenMod/android_external_stlport" remote="github" revision="cm-13.0" />

manups4e said:
ok so.. boringssl-compat is a must if you want to build with lollipop blobs.
external_stlport is needed to build libs for qualcomm devices.
this is what you need to put into your local_manifest.xml
Code:
<project path="external/sony/boringssl-compat" name="CyanogenMod/android_external_sony_boringssl-compat" remote="github" revision="cm-13.0" />
<project path="external/stlport" name="CyanogenMod/android_external_stlport" remote="github" revision="cm-13.0" />
Click to expand...
Click to collapse
Thx your help:fingers-crossed:
The zip can boot now.