Related
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.
For newer builds see http://forum.xda-developers.com/showthread.php?t=2687229
WARNING: This is an experimental build!
Usual CM 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
Audio
Rotation
Storage
Camera
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 CM 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
CM 10.2:
https://code.google.com/p/tab89cm/downloads/list?q=cm10.2
Sources:
https://github.com/CyanogenMod
https://github.com/pershoot
https://github.com/cmorlok
My local_manifest.xml:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="cmorlok/android_kernel_samsung_p5" path="kernel/samsung/p5" revision="refs/heads/cm-10.1" />
<project name="cmorlok/android_device_samsung_p4-common" path="device/samsung/p4-common" revision="refs/heads/cm-10.2" />
<project name="cmorlok/android_device_samsung_p5" path="device/samsung/p5" revision="refs/heads/cm-10.2" />
<project name="cmorlok/android_device_samsung_p5wifi" path="device/samsung/p5wifi" revision="refs/heads/cm-10.2" />
<project name="cmorlok/proprietary_vendor_samsung" path="vendor/samsung" revision="refs/heads/cm-10.2" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" />
<remove-project name="CyanogenMod/android_build" />
<project name="cmorlok/cm_android_build" path="build" revision="refs/heads/cm-10.2" />
</manifest>
Known issues:
If you want to go back to CM10/9 or restore your backup, you'll have to do the following in recovery (do "install zip" and "choose zip from sdcard" first):
Code:
adb shell
# cd /sdcard/
# rm -rf legacy/
# rm -rf obb/
# mv -f 0/* .
# rm -rf 0/
Reserved for FAQ
Awesome! Looking forward to seeing where this build goes. Thanks for keeping this tab on the cutting edge, C-O-M!
Sent from my LG-VM670 using xda app-developers app
waiting P7300 ver..thx c-o-m to make my 8.9 update:laugh:~~
upconvert said:
Awesome! Looking forward to seeing where this build goes. Thanks for keeping this tab on the cutting edge, C-O-M!
Sent from my LG-VM670 using xda app-developers app
Click to expand...
Click to collapse
I agree! Thanks!
Great work! I'm so glad there are people like you around keeping our tab alive!
What about gapps? Included or just use 4.2-gapps?
Waiting for screen capture, thanks CyanogenMod
Idlekilla said:
Great work! I'm so glad there are people like you around keeping our tab alive!
What about gapps? Included or just use 4.2-gapps?
Click to expand...
Click to collapse
I tried the 4.3 GApps. I guess we will see a lot of errors than (like we did for 4.2, e.g. force close on Google Now, ..).
huynhson said:
Waiting for screen capture, thanks CyanogenMod
Click to expand...
Click to collapse
Why? You won't see any difference to 4.2...
E:Error in sd-card.. installation aborted (status 0) - and that unhealthy android. :/
bkk99213 said:
waiting P7300 ver..thx c-o-m to make my 8.9 update:laugh:~~
Click to expand...
Click to collapse
Here we go.
But I suspect 3G is broken like on CM10.1. Any log files are more than welcome since I don't own a 3G tab to test.
Status 0 error P7310
Sent from my GT-P7310 using xda app-developers app
Idlekilla said:
E:Error in sd-card.. installation aborted (status 0) - and that unhealthy android. :/
Click to expand...
Click to collapse
safariking said:
Status 0 error P7310
Click to expand...
Click to collapse
Sorry guys, I've uploaded the wrong file.
Please redownload and verify MD5sum (22b4f5b79243d884fe25a399aa5dd1df) or SHA1sum (c515e18bd78d5b3c62dc279c9d39e07f37325566).
Idlekilla said:
Great work! I'm so glad there are people like you around keeping our tab alive!
What about gapps? Included or just use 4.2-gapps?
Click to expand...
Click to collapse
C-o-M said:
I tried the 4.3 GApps. I guess we will see a lot of errors than (like we did for 4.2, e.g. force close on Google Now, ..)
Click to expand...
Click to collapse
Added link to GApps in first post. The only issue I had so far is force closes of "Google Text-To-Speech". Will look into that tomorrow.
Flashed so far smooth no issues
Flashed with twrp no problems
Sent from my GT-P7310 using xda premium
Mine turns off when charging reaches 100%. Sometimes if I let screen time out, it won't turn back on; have to restart. Several apps fc. Lost root. Updates through play store error out. Feels smooth and mostly working though. Settings sometimes exits out when loading list of installed apps
Loaded 4.3 gapps. Generally, looks good. Panorama in Camera app is great!
Problems:-
- lost root
- Youtube app no-go
- Google Play Music no-go
- Google Text to Speech prob as well
Thanks for work, C-o-M.
Font seems a little blurry also. Colors seem more vibrant though
-----
Sent from my GT-P7310 CM10 using XDA Premium HD app
Brendo said:
Mine turns off when charging reaches 100%. Sometimes if I let screen time out, it won't turn back on; have to restart.
Click to expand...
Click to collapse
My battery is always at about 20% Will charge later and see if I can reproduce that.
Lost root.
Click to expand...
Click to collapse
Root is fine. If you have trouble, disable it in developer settings, reboot and enable again.
Updates through play store error out.
Click to expand...
Click to collapse
There is some problem with the storage path if you so a (dirty) upgrade. I haven't figure out the root cause. Affects other apps as well. You might also get the warning that some Uids are wrong and your system will be unstable.
Probably deleting data for some android system apps will solve that, but I don't have the time to try.
Do a factory reset and you'll be fine. You can restore your apps later with TitaniumBackup or Helium, but ensure that you restore the app data only on selected apps if you really need it.
linw said:
Loaded 4.3 gapps. Generally, looks good. Panorama in Camera app is great!
Problems:-
- lost root
Click to expand...
Click to collapse
See above.
- Youtube app no-go
Click to expand...
Click to collapse
Will test today.
- Google Play Music no-go
Click to expand...
Click to collapse
Weil test today.
YouTube in HQ almost no lag (tested with gangnam style and gentleman)
Play store updates are fine after wiping
No turning off at 100% charging
Everything else is so smooth thanks!!!
Sent from my GT-P7310 using xda premium
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.
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.)
Here we go again! Lollipop for the tenderloin, who'd have thought?
Expect bugs, likely the same ones you experienced in kitkat. Short buglist:
- Selinux is in permissive mode
- Camera is busted
If you have problems flashing, chances are your /system/ volume isn't big enough. I went to 1gb for it now. Jcsullins' TPToolbox can make these changes for you. Its pretty much awesome.
Beware: this takes a LOOOOONG time to boot the first time (and every subsequent flash). Be patient! It runs really nice though once it boots.
I recommend flintman's TWRP with mtp and f2fs support:
http://evervolv.com/get/FLINTMAN-TWRP-touch-data_media-SELINUX-f2fs-2.8.4.0-02-11-2015-1.zip (flashable via your current recovery)
ROM downloads here:
http://www.invisiblek.org/roms/cm-12.0/tenderloin/
Twitterbot: https://twitter.com/invisiblek_cm
Gapps:
http://wiki.cyanogenmod.org/w/Google_Apps
Source:
Kernel Source | Device tree
Roll your own!
If you'd like to build this rom yourself, here's what you need:
In your manifest:
Code:
<project name="invisiblek/proprietary_vendor_hp" path="vendor/hp" />
<project name="invisiblek/android_kernel_hp_tenderloin" path="kernel/hp/tenderloin" />
<project name="invisiblek/android_device_hp_tenderloin" path="device/hp/tenderloin" />
<project name="CyanogenMod/android_hardware_atheros_wlan" path="hardware/atheros/wlan" />
Cherry Picks:
Code:
http://review.cyanogenmod.org/#/c/82223/
http://review.cyanogenmod.org/#/c/82661/
http://review.cyanogenmod.org/#/c/82668/
http://review.cyanogenmod.org/#/c/85519/
http://review.cyanogenmod.org/#/c/85524/
http://review.cyanogenmod.org/#/c/85571/
Sweet! Another Lollipop Build!
For what it's worth, @flintman has build working with Netflix and YouTube. Hopefully you can glean from him the tweaks to make your Rom work as well.
I will have to kick the tires on this build as well to see how it compares to Evervolv. Thanks for making the leap and continuing the development of Android on the HP TouchPad!
--McBean
Awesome news. Gotta try it out.
thanks, i wanted to test this, but i couldn't.
I was running evervolv preview, so i completely wiped my TP with toolbox.
I'm facing a weird issue now. i can't install android. no matter what recovery i use, /system cannot be mounted
Solved.
Nice. First cm for touchpad.
BTW: does this rom access both sdcards?
Thanks.
Sent from my LG-D415 using XDA Premium App
i tried intall cm 12 with team win recovery project v2.8.30
i got error unable to mount , /system
E:error executing update binary in zi/external_/cm12/cm-12-20150104-unofficical-tenderlion.zip
For all those having failed to flash the new rom, have you resized the partition as specified in the OP ?
vinukondamahesh said:
i tried intall cm 12 with team win recovery project v2.8.30
i got error unable to mount , /system
E:error executing update binary in zi/external_/cm12/cm-12-20150104-unofficical-tenderlion.zip
Click to expand...
Click to collapse
You have to increase system partition size with tp toolbox first.
ya I did it thank you, everything is fine battery drain is high
Sent from my HTC Sensation 4G using XDA Free mobile app
Setting CPU speeds
I can't find where to change the CPU speeds.
heavyt said:
I can't find where to change the CPU speeds.
Click to expand...
Click to collapse
Kernel tuner works. Or trickster mod. Both free on play store.
inorder to work fully some of the apps need superuser .....i tried downloading from google play, nothing is working properly in googleplay???????? its there app to install?
vinukondamahesh said:
inorder to work fully some of the apps need superuser .....i tried downloading from google play, nothing is working properly in googleplay???????? its there app to install?
Click to expand...
Click to collapse
what do you mean by "nothing is working properly" ? GPlay works for me, it just takes years to install apps but it works.
have you tried the SuperSU flashable Zip instead of GPlay install ?
U r misunderstood my sentence ,may be my sentence wrong.......
Wat I mean is I have download superuser from Google play its not working... So I made a search in xda I see so many links which r alpha built so I asked for correct app to install
Sent from my Touchpad using XDA Free mobile app
vinukondamahesh said:
U r misunderstood my sentence ,may be my sentence wrong.......
Wat I mean is I have download superuser from Google play its not working... So I made a search in xda I see so many links which r alpha built so I asked for correct app to install
Sent from my Touchpad using XDA Free mobile app
Click to expand...
Click to collapse
Install this one, let it update binaries and reboot if needed, and you're done.
ya it's working now thank you, I installed link u have given before..
Sent from my HTC Sensation 4G using XDA Free mobile app
invisiblek said:
--SNIP--
Beware: this takes a LOOOOONG time to boot the first time (and every subsequent flash). Be patient!
--SNIP--
Click to expand...
Click to collapse
About how long is LOOOOONG?
shumash said:
About how long is LOOOOONG?
Click to expand...
Click to collapse
A little over 15 mins using the PA "micro" gapps as mentioned in the OP.
A little over 22 mins using the "standard" gapps (i.e. gapps-lp-20141109-signed.zip).
jcsullins said:
A little over 15 mins using the PA "micro" gapps as mentioned in the OP.
A little over 22 mins using the "standard" gapps (i.e. gapps-lp-20141109-signed.zip).
Click to expand...
Click to collapse
Restoring a Lollipop backup of evervolv took me 20min in total just for booting + 10min restoring, so it can take a very long time... I wonder what's making those roms so slow to boot/install/restore. It's almost as worse as my old jailbreaked iPhone 3GS just in boot time on second and later boot.
Atari-San said:
Restoring a Lollipop backup of evervolv took me 20min in total just for booting + 10min restoring, so it can take a very long time... I wonder what's making those roms so slow to boot/install/restore. It's almost as worse as my old jailbreaked iPhone 3GS just in boot time on second and later boot.
Click to expand...
Click to collapse
The boot times get shorter. Its the same on my phone. First few boots are slow.
Sent from my HP Touchpad running Evervolv Lollipop 5.0