OKay So I thought I would try to port the latest beta of L to our OnePlus One. Never really ported before and mainly followed this thread here: http://forum.xda-developers.com/showthread.php?t=1908008
Currently I have it installing and booting to the boot animation and playing the boot animation (whooo) but thats as far as it goes. Unfortunately usb isn't recognized when I plug it in. Is there any way I can get some sort of log?
Its based on the latest nexus 5 L rom.
here is the zip file. Its broken, under no circumstance should you install this unless you are a developer.
Code:
DO NOT INSTALL IF YOU AREN'T A DEVELOPER
AOSP BASE
PA BASE
Current logcat on boot for PA:
http://pastebin.com/c5J0cmQ8
Can't get logcat on boot for AOSP base
Instead of AOSPA try using the official Oneplus AOSP rom as base. Let me know.
Nice of you that you even tried it! Maybe you developers should port this together in teamwork? Everybody has problems with L on the OPO, maybe together you can solve them
Did you tried it with OnePlus AOSP?
You guys might benefit from the discussion here:
http://forum.xda-developers.com/showthread.php?t=2829974
Transmitted via Bacon
---------- Post added at 08:12 PM ---------- Previous post was at 08:08 PM ----------
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon
phoenixita said:
Instead of AOSPA try using the official Oneplus AOSP rom as base. Let me know.
Click to expand...
Click to collapse
just tried with aosp and although file structures and update scripts seemed more similar, I can't get a logcat and I am still stuck at a bootanimation
aeppacher said:
just tried with aosp and although file structures and update scripts seemed more similar, I can't get a logcat and I am still stuck at a bootanimation
Click to expand...
Click to collapse
There are some error with camera and sound :
E/AudioDaemon( 245): Open /proc/asound/card---/state failed : No such file or directory
[...]
E/mm-camera( 243): vpe_module_create_vpe_ctrl:141, failed, cannnot create vpe hardware instance
E/mm-camera( 243): vpe_module_init:34 failed
E/mm-camera( 243): c2d_module_init:28 name=c2d
E/mm-camera( 243): c2d_module_init:67: info: C2D module_init successful
E/mm-camera-img( 243): cac_comp_load:656] Error opening CAC library
E/mm-camera( 243): module_cac_init:1028] Error rc -6
E/mm-camera( 243): pproc_module_init:2175] cac module create failed
I don't know exactly why...
Maybe tomorrow and next week I'll try too
@aeppacher are you using latest android 5.0 preview LPX13D?
eugenioxx said:
There are some error with camera and sound :
E/AudioDaemon( 245): Open /proc/asound/card---/state failed : No such file or directory
[...]
E/mm-camera( 243): vpe_module_create_vpe_ctrl:141, failed, cannnot create vpe hardware instance
E/mm-camera( 243): vpe_module_init:34 failed
E/mm-camera( 243): c2d_module_init:28 name=c2d
E/mm-camera( 243): c2d_module_init:67: info: C2D module_init successful
E/mm-camera-img( 243): cac_comp_load:656] Error opening CAC library
E/mm-camera( 243): module_cac_init:1028] Error rc -6
E/mm-camera( 243): pproc_module_init:2175] cac module create failed
I don't know exactly why...
Maybe tomorrow and next week I'll try too
@aeppacher are you using latest android 5.0 preview LPX13D?
Click to expand...
Click to collapse
yes I am. I am posting my attempt at the aosp port with the LPX13D as well. Adb isn't grabbing a logcat for me unfortunately
Hopefully devs can help this would be sweet
Hit Thanks if I Helped
-_-NAMELESS ROM 1+1-_-
Hey man i'm no dev, but I just shared your post on Reddit (r/Android and r/oneplus) hopefully more devs will see this and come assist you I would love a port!
Just like previously mentioned I think you guys would benefit from the discussion in the thread previously posted. Better yet pm the developer who recently tried so you at least rule out some things that may have been previously attempted. Good luck guys
You cant port different version of Android by drag-and-droping system folders.
It'll probably be easier once retail Lollipop is out and open sourced on AOSP project. But TBH Cyanogenmod historically has put out builds really fast for nexus devices and ours is nexus-ish. I'll try my luck with kanging CM once they put something out for the N5 or N6.
---------- Post added at 07:20 PM ---------- Previous post was at 07:19 PM ----------
CraZY_BoY^ said:
You cant port different version of Android by drag-and-droping system folders.
Click to expand...
Click to collapse
Ha, no.
CraZY_BoY^ said:
You cant port different version of Android by drag-and-droping system folders.
Click to expand...
Click to collapse
This
Sent from my X9006 using XDA Free mobile app
CraZY_BoY^ said:
You cant port different version of Android by drag-and-droping system folders.
Click to expand...
Click to collapse
suraj.das said:
This
Click to expand...
Click to collapse
Yes, this is not what they're doing. That would be idiotic. They're trying to port it.
Alzoids said:
Yes, this is not what they're doing. That would be idiotic. They're trying to port it.
Click to expand...
Click to collapse
Check the link the OP has used to port. It's exactly what he's doing!
You need more skills than that to accomplish this!
TiVON said:
Check the link the OP has used to port. It's exactly what he's doing!
You need more skills than that to accomplish this!
Click to expand...
Click to collapse
Should have included a "/s" I guess.
Sorry man, but when you are making this big of a switch. Especially different device AND different version of android, there is more that the drag and drop tutorial to this. You actually need to know the languages its developed is so you can find what's wrong with it and in turn, you can create your own fix. (Simple terms here)
Basically, you need to be able to write a compliant device tree and kernel that can compile with the new source.
TiVON said:
Check the link the OP has used to port. It's exactly what he's doing!
You need more skills than that to accomplish this!
Click to expand...
Click to collapse
sorry to go off topic but your DP suits the situation lol
Related
This thread is only for Developers.
If you're looking for help or download links then this is not the right place.
User Thread: http://forum.xda-developers.com/showthread.php?t=2036229
How to build:
http://teamhacksung.org/wiki/index.php/CyanogenMod10.1:How_to_build
Sources:
https://github.com/cyanogenmod/android_device_samsung_i9100
https://github.com/cyanogenmod/android_device_samsung_galaxys2-common
https://github.com/cyanogenmod/android_kernel_samsung_smdk4210
https://github.com/cyanogenmod/android_hardware_samsung
How to submit patches?
http://wiki.cyanogenmod.org/wiki/Howto:_Gerrit
No, we don't accept pull requests!
Sorry, wrong post, please delete.
When is the 911/112/Emergency call going to be solved?
http://code.google.com/p/cyanogenmod/issues/detail?id=5700
This has been an EMERGENCY issue for 7 month's, and I dont wanna disrespect you guys. But this is something what really needs to be fixed. If we wanna use the rom we can't call the emergency line in a situation.
Provider: Vodafone NL
GT9100
RR 3.1.3 (every other CM rom also gives the "invalid number" error.
domingoo said:
When is the 911/112/Emergency call going to be solved?
http://code.google.com/p/cyanogenmod/issues/detail?id=5700
This has been an EMERGENCY issue for 7 month's, and I dont wanna disrespect you guys. But this is something what really needs to be fixed. If we wanna use the rom we can't call the emergency line in a situation.
Provider: Vodafone NL
GT9100
RR 3.1.3 (every other CM rom also gives the "invalid number" error.
Click to expand...
Click to collapse
no dev is on vodafone nl or kpn so chances that this will get fixed are not very high.
reminder: nightlies are experimental.
Sent from my Nexus 4 using xda app-developers app
codeworkx said:
no dev is on vodafone nl or kpn so chances that this will get fixed are not very high.
reminder: nightlies are experimental.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
This has also been a problem with STABLE roms. I've also understood that there were plans to pull the CM9 stable because of this bug, but that has not happend.
Besides this people have also mentioned it's also a problem on other networks besides Vodavone NL or KPN NL, so don't pull the excuse that there are no devs available on just these networks. I have no doubt in my mind that if it had been mentioned that there are no devs with these connections people would have been willing to help in any way possible. Instead of this the problem is just ignored for months on end.
I've found that Trebuchet launcher doesn't have those graphic artifacts, caused by the placebocomposer. However, Nova Launcher has them and that makes me think you've found a way to fix the glitches in certain apps. If so, is it possible to implement these fixes to the daydream clock app? Also, I think that the analog daydream clock doesn't always glitch because it updates the screen every second, while the digital one does so every minute. Maybe if you make the digital clock update every second, the artifacts won't show?
Can't pull files
I was trying to build cm10.1 for i9100 for the first time and I get an error message about libtvout and libcamera not being pulled from device. Is there any known issue or am I doing something wrong?
I am following the new Wiki to the letter, but I can't get it to work.
http://wiki.cyanogenmod.org/w/Build_for_i9100
Prepare the device-specific code
After the source downloads, type:
$ source build/envsetup.sh
$ breakfast i9100
Click to expand...
Click to collapse
When I type
Code:
breakfast i9100
I get this error
Code:
** Don't have a product spec for: 'cm_i9100'
** Do you have the right repo manifest?
In the older Wiki's I see they use a local_manifest.xml.
Is this still necessary? It's not mentioned in the new Wiki at all....
CRXed said:
I am following the new Wiki to the letter, but I can't get it to work.
http://wiki.cyanogenmod.org/w/Build_for_i9100
When I type
Code:
breakfast i9100
I get this error
Code:
** Don't have a product spec for: 'cm_i9100'
** Do you have the right repo manifest?
In the older Wiki's I see they use a local_manifest.xml.
Is this still necessary? It's not mentioned in the new Wiki at all....
Click to expand...
Click to collapse
Try this guide http://teamhacksung.org/wiki/index.php/CyanogenMod10.1:How_to_build
Complete error
Code:
[email protected]:~/android/system$ . build/envsetup.sh
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/generic/mips/vendorsetup.sh
including device/generic/x86/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including sdk/bash_completion/adb.bash
[email protected]:~/android/system$ breakfast i9100
including vendor/cm/vendorsetup.sh
ls: cannot access device/*/i9100/cm.mk: No such file or directory
build/core/product_config.mk:234: *** Cannot locate config makefile for product "cm_i9100". Stop.
Device i9100 not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_samsung_i9100
Default revision: cm-10.1
Checking branch info
Adding dependency: CyanogenMod/android_device_samsung_i9100 -> device/samsung/i9100
Using default branch for android_device_samsung_i9100
Syncing repository to retrieve project.
error: project device/samsung/i9100 not found
Repository synced!
Looking for dependencies
Dependencies file not found, bailing out.
Done
ls: cannot access device/*/i9100/cm.mk: No such file or directory
build/core/product_config.mk:234: *** Cannot locate config makefile for product "cm_i9100". Stop.
** Don't have a product spec for: 'cm_i9100'
** Do you have the right repo manifest?
What is wrong?
---------- Post added at 03:18 PM ---------- Previous post was at 02:38 PM ----------
niko0o said:
Try this guide http://teamhacksung.org/wiki/index.php/CyanogenMod10.1:How_to_build
Click to expand...
Click to collapse
Trying that now, but shouldn't CM's own Wiki have the right information?
I get the idea it is missing something, but I don't know what exactly....
CRXed said:
Complete error
Code:
[email protected]:~/android/system$ . build/envsetup.sh
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/generic/mips/vendorsetup.sh
including device/generic/x86/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including sdk/bash_completion/adb.bash
[email protected]:~/android/system$ breakfast i9100
including vendor/cm/vendorsetup.sh
ls: cannot access device/*/i9100/cm.mk: No such file or directory
build/core/product_config.mk:234: *** Cannot locate config makefile for product "cm_i9100". Stop.
Device i9100 not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_samsung_i9100
Default revision: cm-10.1
Checking branch info
Adding dependency: CyanogenMod/android_device_samsung_i9100 -> device/samsung/i9100
Using default branch for android_device_samsung_i9100
Syncing repository to retrieve project.
error: project device/samsung/i9100 not found
Repository synced!
Looking for dependencies
Dependencies file not found, bailing out.
Done
ls: cannot access device/*/i9100/cm.mk: No such file or directory
build/core/product_config.mk:234: *** Cannot locate config makefile for product "cm_i9100". Stop.
** Don't have a product spec for: 'cm_i9100'
** Do you have the right repo manifest?
What is wrong?
---------- Post added at 03:18 PM ---------- Previous post was at 02:38 PM ----------
Trying that now, but shouldn't CM's own Wiki have the right information?
I get the idea it is missing something, but I don't know what exactly....
Click to expand...
Click to collapse
Where you able to compile in the end? I have not been at all following any guide
I'm still strying!
Turned out my Repo Sync was not complete after all....
I got a tip from someone to use
Code:
repo sync -j1
And then finally it pulled in the Samsung directory as well.
CRXed said:
I'm still strying!
Turned out my Repo Sync was not complete after all....
I got a tip from someone to use
Code:
repo sync -j1
And then finally it pulled in the Samsung directory as well.
Click to expand...
Click to collapse
Hm... That's interesting. So do you have the samsung specific folder synced now? Is it the one under /devices?
Sent from my GT-I9100 using xda app-developers app
juanono said:
Hm... That's interesting. So do you have the samsung specific folder synced now? Is it the one under /devices?
Click to expand...
Click to collapse
Yes!
Could someone. please, fix the mdpi lock screen and the sim lock screen or is it not supported anymore?
Since about cm10.1 - no cm10 build downloads for i9100 are available anymore so I can't test whether it started there - the irremovable widget (by default a clock but can be altered) on the lock screen has a fixed amount of space reserved whose relative size increases by lowering the dpi. At 160 dpi it accounts for half of the screen which makes the a pattern lock and the sim lock more difficult to use.
Since it is possible to have maximized widgets, it shouldn't be that difficult to fix.
Best would be to keep the current layout but let the pattern, pin or password input get focus and maximize and adding an option to completely disable lock screen widgets. Although resizing of the mdpi layout would be nice I don't know how that would affect build configurations using other dpi settings between 160 and 200.
The "Lockscreen Policy" app which claims to disable the widgets does so only partly. Except for the default clock it disables the running of widgets and the editing of the preexisting transparent panels so it doesn't change the layout settings.
siseam said:
Could someone. please, fix the mdpi lock screen and the sim lock screen or is it not supported anymore?
Since about cm10.1 - no cm10 build downloads for i9100 are available anymore so I can't test whether it started there - the irremovable widget (by default a clock but can be altered) on the lock screen has a fixed amount of space reserved whose relative size increases by lowering the dpi. At 160 dpi it accounts for half of the screen which makes the a pattern lock and the sim lock more difficult to use.
Since it is possible to have maximized widgets, it shouldn't be that difficult to fix.
Best would be to keep the current layout but let the pattern, pin or password input get focus and maximize and adding an option to completely disable lock screen widgets. Although resizing of the mdpi layout would be nice I don't know how that would affect build configurations using other dpi settings between 160 and 200.
The "Lockscreen Policy" app which claims to disable the widgets does so only partly. Except for the default clock it disables the running of widgets and the editing of the preexisting transparent panels so it doesn't change the layout settings.
Click to expand...
Click to collapse
You can download CM10 nightly from here http://goo.im/devs/cm/i9100/nightly .
niko0o said:
You can download CM10 nightly from here http://goo.im/devs/cm/i9100/nightly .
Click to expand...
Click to collapse
Thanks, I didn't notice goo hosted so many roms.
I tested the roms and the new lock screen is introduced with the first cm10.1 nightly. So, I guess, it may be a jellybean design flaw since Google doesn't support modifications anyway.
So I hope someone picks up this bug, especially using more complex patterns is pretty tedious when they're so small.
niko0o said:
Try this guide http://teamhacksung.org/wiki/index.php/CyanogenMod10.1:How_to_build
Click to expand...
Click to collapse
This link used to work, but now seems to be redirected, with a typo that doesn't work, to the CyanogenMod wiki. So does the one on the first page headed "How To Build".
Also the CyanogenMod wiki (http://wiki.cyanogenmod.org/w/Build_for_i9100) has somewhat different instructions on downloading the source code. I've not tried them because the teamhacksung wiki worked fine for me before it was redirected.
Hey guys , on the latest nightly , 21st march , the proximity sensor and accelerometer arent always working , had to downgrade to 20 march , im on stock cm10.1. Anyone else having this issuse ?
Also , did the 22nd march nghtly was launched ? I dont seem to find any new updates.
EDIT: 23rd march update fixed everything , thanks ! you guys rock !
Sent from my GT-I9100 using xda app-developers app
MMS not working
Hi!
I installed 10.1-20130327-NIGHTLY-i9100 and MMS messages are not working (receive or send). Looking at adb logcat output, I see:
Code:
W/TransactionService( 3806): Exception occurred while handling message: { what=1 when=-14ms arg1=1 obj=transactionType: 2 uri: content://mms/6 pushData: null mmscUrl: null proxyAddress: null proxyPort: 0 }
W/TransactionService( 3806): java.lang.NullPointerException
W/TransactionService( 3806): at com.android.mms.transaction.TransactionSettings.<init>(TransactionSettings.java:92)
W/TransactionService( 3806): at com.android.mms.transaction.TransactionService$ServiceHandler.handleMessage(TransactionService.java:640)
W/TransactionService( 3806): at android.os.Handler.dispatchMessage(Handler.java:99)
W/TransactionService( 3806): at android.os.Looper.loop(Looper.java:137)
W/TransactionService( 3806): at android.os.HandlerThread.run(HandlerThread.java:60)
This pointed me in the direction of APN settings, which are all fine (they were preserved during installation, and I'm coming from stock 4.0.3 Samsung OS).
I then noticed that the default APN (used for data), had the value of "APN type" set to "default,supl,mms". I erased all of the values, hoping that the other APN will be taken -- the one with the MMS settings, but still nothing.
Any ideas what to try next? It would be great if I could debug the transaction service to see why it can't get the APN settings...
Regards,
Miha.
---------- Post added at 11:49 AM ---------- Previous post was at 11:32 AM ----------
mihaval said:
Any ideas what to try next? It would be great if I could debug the transaction service to see why it can't get the APN settings...
Click to expand...
Click to collapse
Did some more digging. Install GOSMS pro app, to try that. I got a different bunch of exceptions:
Code:
E/DatabaseUtils( 2411): Writing exception to parcel
E/DatabaseUtils( 2411): java.lang.SecurityException: No permission to write APN settings: Neither user 10035 nor current process has android.permission.WRITE_APN_SETTINGS.
And that led me to this SO question. So I guess there needs to be a way to specify those permission for the MMS (Messaging) application somehow?
can not find symbol when compiling cm 11.0 on debian.
any help will be greatful.
Code:
packages/apps/Settings/src/com/android/settings/hardware/DisplayColor.java:109: cannot find symbol
symbol : method getDefValue()
location: class org.cyanogenmod.hardware.DisplayColorCalibration
int defaultValue = DisplayColorCalibration.getDefValue();
^
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
tomheng said:
can not find symbol when compiling cm 11.0 on debian.
any help will be greatful.
Code:
packages/apps/Settings/src/com/android/settings/hardware/DisplayColor.java:109: cannot find symbol
symbol : method getDefValue()
location: class org.cyanogenmod.hardware.DisplayColorCalibration
int defaultValue = DisplayColorCalibration.getDefValue();
^
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
Click to expand...
Click to collapse
I got the same error just now and I'm trying to track down the java class it's referring to. Perhaps getDefValue has changed in it.
---------- Post added at 09:38 AM ---------- Previous post was at 09:32 AM ----------
The missing value is in the "common" device folder for your hardware. In my case, /device/lge/g2-common
specifically, it's in the file /device/lge/g2-common/cmhw/org/cyanogenmod/hardware/DisplayColorCalibration.java
It SHOULD work if you add in the proper support for getDefValue as found in THIS COMMIT
I'm going to make the changes and give it another try
---------- Post added at 10:25 AM ---------- Previous post was at 09:38 AM ----------
Well, my G2 build (VZW vs980) completed. Copied it to my device and flashed. Apart from an odd glitch where the vibration notification was going nonstop until I manually adjusted the audio mode (to vibrate only, then back to sound), everything works well.
i recomipiled successfully, after modify the file according your answer.
thanks a lot, and i will move on my ROM
tomheng said:
i recomipiled successfully, after modify the file according your answer.
thanks a lot, and i will move on my ROM
Click to expand...
Click to collapse
Very glad to hear it!
RandomPooka said:
I got the same error just now and I'm trying to track down the java class it's referring to. Perhaps getDefValue has changed in it.
---------- Post added at 09:38 AM ---------- Previous post was at 09:32 AM ----------
The missing value is in the "common" device folder for your hardware. In my case, /device/lge/g2-common
specifically, it's in the file /device/lge/g2-common/cmhw/org/cyanogenmod/hardware/DisplayColorCalibration.java
It SHOULD work if you add in the proper support for getDefValue as found in THIS COMMIT
I'm going to make the changes and give it another try
Click to expand...
Click to collapse
Old but gold. Thanks mate. Was building cm11 for an old device.
lee.wp14 said:
Old but gold. Thanks mate. Was building cm11 for an old device.
Click to expand...
Click to collapse
WOW. I love zombies
Can't even remember the last time I used or even still had that old LG G2!!
Q&A for [ROM][UB][AOSP 4.4.4_r2 -V4.1] Sony Xperia P Android Open Source Xperia ROM
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
help!!!
will not let me install the kernel, I do not start by flashtool and mobile me, I'm doing it from the stock rom ... I had installed the rom-Experience-V1 Sirius, you can install the rom AOSX-4.4.4_r2-nypon -V4.1 from Sirius? ... thanks for your help.
which rom between aosp and cm11 is more stable for daily use
jafa68 said:
will not let me install the kernel, I do not start by flashtool and mobile me, I'm doing it from the stock rom ... I had installed the rom-Experience-V1 Sirius, you can install the rom AOSX-4.4.4_r2-nypon -V4.1 from Sirius? ... thanks for your help.
Click to expand...
Click to collapse
Just do this:
Download the ROM
Extract boot.img and flash it
Copy the ROM to your SD Card
Boot into recovery
Wipe data, cache, dalvik cache
Install the ROM
Reboot
First post
---------- Post added at 04:33 PM ---------- Previous post was at 04:28 PM ----------
tefl0n said:
which rom between aosp and cm11 is more stable for daily use
Click to expand...
Click to collapse
I use only AOSP 4.4.4_r2 -V4.1, and it's really comfortable and stable.
I don't know any trouble at this moment
I have been using it since release .
Keiichiart said:
I use only AOSP 4.4.4_r2 -V4.1, and it's really comfortable and stable.
I don't know any trouble at this moment
I have been using it since release .
Click to expand...
Click to collapse
I'm having some trouble pairing phone and car via blutooth with latest CM11 builds... do you know if this feature is working correctly in AOSP 4.4.4_r2 -V4.1?
Hi guys,
having probs with my xperia p .
unlocked the boorloader .
Flashed the boot.img with Flashtool like shown in this thread http://forum.xda-developers.com/showthread.php?t=1963961
the phone showed the logo and now the home button on the light bar is lit and the backlight of the screen is on.
no other response. Please advice
Keiichiart said:
Just do this:
Download the ROM
Extract boot.img and flash it
Copy the ROM to your SD Card
Boot into recovery
Wipe data, cache, dalvik cache
Install the ROM
Reboot
First post
---------- Post added at 04:33 PM ---------- Previous post was at 04:28 PM ----------
Click to expand...
Click to collapse
Can't flash the rom.zip
@percy_g2 today i just tried to flash this rom and have some bragging rights 'bout my xperia p so i downloaded the rom,extracted boot.img from the .zip (I deleted the boot.img from the .zip then archived it again when i finished from flashing boot.img via fastboot),Then all of a sudden when i tried to flash the .zip to my phone thru cwm they told me status 7 installation aborted what should i do now?.
Actually my phone got soft bricked and now i fixed it again.
Xperia P won't Boot into recovery
Hello there, I'm a complete noob here, so please help me. thanks in advance.
I managed to unlock the bootloader, and did these :
1- Download the ROM
2- Extract boot.img and flash it
3- Copy the ROM to your SD Card
4- Boot into recovery.
Click to expand...
Click to collapse
but when I try to boot into recovery (pressing power key first, then pressing volme up key repeatedly), it shows the sony logo with "powered by aosx" logo in the end... after one second, it goes away and nothing happens..
I don't know what i did wrong and how can I make it right.
thanks.
Edit: I should have pressed power several times... figured it out... thanks.
First, thanks so much for the the ROM, glad I can update the sony 4.1 to some little more modern 4.4. Now, I have two newbie questions.
Can the ROM influence the GPS? In OSMAnd, I am now off by 50 metres from my actual location but it was working quite reliable on the old sony version. I'm a bit too lazy to install hundreds of different ROMs or to go back etc, so just checking if maybe someone has a thought?
Also I have a weird glitch with th gesture trail in the Google Keyboard, basically it doesn't forget the lines I have already drawn in the past on new words. I've attached a screenshot. The blue stuff there is *not* what I drew for this word, which was just a swipe left. Quite unusable
Thanks!
Amendment, apk from http://forum.xda-developers.com/android/apps-games/lollipop-keyboard-phones-root-t2910268 also has the same issue for me
Another issue, this app https://play.google.com/store/apps/details?id=de.rbb.sandmann installs and loads fine, but actually watching the videos doesn't work. logcat sadly is not very helpful....
Code:
+++ LOG: malformed log message
I/Unity (30104): play bubble : folge
I/Unity (30104):
I/Unity (30104): (Filename: ./artifacts/AndroidManagedGenerated/UnityEngineDebug.cpp Line: 49)
I/Unity (30104):
I/Unity (30104): New camera mode : FilmeBubble
I/Unity (30104):
I/Unity (30104): (Filename: ./artifacts/AndroidManagedGenerated/UnityEngineDebug.cpp Line: 49)
I/Unity (30104):
I/wpa_supplicant( 3595): wlan0: WPA: Group rekeying completed with [GTK=TKIP]
I/libblt_hw( 2846): Library opened (handle = 8, fd = 62)
I/libblt_hw( 2846): Library closed (handle = 10, fd = 51)
E/MediaPlayer(30104): pause called in state 1
E/MediaPlayer(30104): error (-38, 0) <--- here's the error
W/MediaPlayer(30104): mediaplayer went away with unhandled events
W/BufferQueue( 2846): [SurfaceView] cancelBuffer: BufferQueue has been abandoned!
I/libblt_hw( 2846): Library opened (handle = 9, fd = 51)
I/libblt_hw( 2846): Library closed (handle = 8, fd = 62)
I/Unity (30104): New camera mode : IntroEnd
I/Unity (30104):
I/Unity (30104): (Filename: ./artifacts/AndroidManagedGenerated/UnityEngineDebug.cpp Line: 49)
I/Unity (30104):
I/Unity (30104):
I/Unity (30104):
I/Unity (30104): (Filename: ./artifacts/AndroidManagedGenerated/UnityEngineDebug.cpp Line: 49)
I/Unity (30104):
this works in stock rom. wonder if it could be missing some codecs etc?
Wifi with static ip
I just installed lastest version of this ROM: it seems great, but i have an issues with wifi: I need to connect with a static ip, but it doesn't work.
I did a wrong configuration of gateway: it works correctly now!
Can't boot, can't get into recovery with AOSX v4.1
Hey, your boot.img is probably corrupted. I flashed it after unlocking bootloader, but the device will never start. It freezes either at the screen with SONY logo and green robot, or afterwards it goes black (with backlight on) and hangs there. And no way to get into recovery - it won't react to volume keys
EDIT: Woops, it should've been the POWER BUTTON. mention this somewhere, please.
HTML5 video does not work; screen rotation faulty
I have noticed that HTML5 video does not work in any browser (tried stock, Opera and Firefox). Just video encoded with H264 for sure works with HW decoder in MX Player, but neither codec is supported in browsers for some reason. WebGL works in Firefox, but not in Opera or stock.
Another thing: screen auto-rotation mostly does not work. It works only in SatStat app from F-Droid repo for some reason. If an app for manual rotation is installed, you can switch it manually.
tefl0n said:
which rom between aosp and cm11 is more stable for daily use
Click to expand...
Click to collapse
aosp is more smooth than cm11 and doesn't have any extra features so its basically pure android, on the other hand cm11 is a tad bit slower but has alot of useful features
---------- Post added at 11:35 AM ---------- Previous post was at 11:29 AM ----------
Venseiiz said:
Another thing: screen auto-rotation mostly does not work. It works only in SatStat app from F-Droid repo for some reason. If an app for manual rotation is installed, you can switch it manually.
Click to expand...
Click to collapse
Auto rotation will only work if auto brightness is turned on, this is for all kitkat and up versions of android for xperia p, I'm not sure as to why but thats how its always been.
I have tried to manage to make a build of cm11
Links : http://d-h.st/tuND
But i get status 7 error for this
so i edited my tree a little bit and tried to build again
here's my tree : https://github.com/missesmr/android_device_zenfone5
Kernel : https://github.com/ZenfoneArea/android_kernel_asus_zenfone5
i used X86 deconfig
If anyone can help me , i would be happy
Great! I tried to build with shakalaca's tree, succeed but didnt past the asus oem splash will try today. Will let you know.
deleted
sai dev said:
I have tried to manage to make a build of cm11
Links : http://d-h.st/tuND
But i get status 7 error for this
so i edited my tree a little bit and tried to build again
here's my tree : https://github.com/missesmr/android_device_zenfone5
Kernel : https://github.com/ZenfoneArea/android_kernel_asus_zenfone5
i used X86 deconfig
If anyone can help me , i would be happy
Click to expand...
Click to collapse
http://www.mediafire.com/download/x33wtk1w9ohgm4z/A500CG_PHILZTOUCH_RECOVERY_WW-2.21.40.44.7z
Try this recovery with external sdcard support(ext4 formatted).
If you get status 7, try to wipe data.
X AnwarMov said:
hy @sai dev i'm succesfully build CM 11 from your source
i using asus Zenfone 4 A400CG
THANKS mate , but i found bugs . systemUi has stoped , telephony stoped .
how to fix it mate . ?
anyone can help me ?
Click to expand...
Click to collapse
Can you post logcat please? If you dont know you can search it on google.
deleted
X AnwarMov said:
hii @smgdev logcat in attachments
. i hope anyone help me
Click to expand...
Click to collapse
E/hwcomposer( 177): int hwc_eventControl(hwc_composer_device_1*, int, int, int): unsupported event 1
This is your error. Same as cm11 zenfone 5. Hwcomposer is broken in intel patches so you can try to replace hwcomposer.so file from your original rom and try to flash it again. It is something like hwcomposer.devicecode.so device code is a400cg I guess. I will update you on this. Good luck.
smgdev said:
E/hwcomposer( 177): int hwc_eventControl(hwc_composer_device_1*, int, int, int): unsupported event 1
This is your error. Same as cm11 zenfone 5. Hwcomposer is broken in intel patches so you can try to replace hwcomposer.so file from your original rom and try to flash it again. It is something like hwcomposer.devicecode.so device code is a400cg I guess. I will update you on this. Good luck.
Click to expand...
Click to collapse
Any updates?
Hello everyone I managed to build Aosip 9.0 rom for our shamu but the build need some work when I flashed my build I get bootloop so DON'T FLASH IT please only if you know how to help me fix this probleme
DOWNLOAD LINK :
https://mega.nz/#!DmZwEAwJ!mkwTswDbaAkciFIF6rIyNr6y__LQom5aAb6-qmKYvvU
DMESG LOG TXT LINK :
https://gist.github.com/RinGooDz/60569c21d30da4b707735efa2859dd93#file-dmesg-bootloop
@electroshmok told me that the probleme from the dmesg log txt is here :
[ 2.770511] init: Command 'start configstore-hal-1-0' action=late-fs (/init.shamu.rc:72) took 0ms and failed: service configstore-hal-1-0 not found
[ 2.770577] init: Command 'start gralloc-2-0' action=late-fs (/init.shamu.rc:73) took 0ms and failed: service gralloc-2-0 not found
so please to all developers and all who know how to fix this can you please help
- this rom still doesn't boot up so please don't flash it -
help please my first build i tried to fix this myself but this strong for me I'm new to android development @camcory @nitin.chobhe @Wajdi Muhtadi @Neo
Rom source :
https://github.com/AOSiP
Device tree code :
https://github.com/RinGooDz/AOSIP-Device-Tree-for-shamu.git
Kernel tree is from Nitrogen os without any changes : https://github.com/nitrogen-os-devices/android_kernel_moto_shamu.git
Vendor tree is also from Nitrogen os without any changes :
https://github.com/nitrogen-os-devices/android_vendor_motorola.git
You should add the github links for ROM source, your device, kernel, vendor trees.
Nitin
nitin.chobhe said:
You should add the github links for ROM source, your device, kernel, vendor trees.
Nitin
Click to expand...
Click to collapse
I will do it now sir
AmirHRC said:
help please my first build i tried to fix this myself but this strong for me I'm new to android development
Click to expand...
Click to collapse
Perhaps you should do something easier then porting a ROM if you have no experience/skill in doing that.
Judging from your past endeavours this is probably going to lead nowhere if you don't start trying to understand the code and how stuff works.
I can help, but I won't port the ROM for you as I have zero interest in another short lived ROM for shamu.
So as long as you're not going to do serious development with proper links to code and doing own work please refrain from asking me stuff and mentioning me in your threads.
Elektroschmock said:
Perhaps you should do something easier then porting a ROM if you have no experience/skill in doing that.
Judging from your past endeavours this is probably going to lead nowhere if you don't start trying to understand the code and how stuff works.
I can help, but I won't port the ROM for you as I have zero interest in another short lived ROM for shamu.
So as long as you're not going to do serious development with proper links to code and doing own work please refrain from asking me stuff and mentioning me in your threads.
Click to expand...
Click to collapse
you also start from zero bro okey so don't be so serious like this everyone start like this and android development doesn't need a lot of code I managed to build the rom but its stuck at the bootanimation i tried to fix the probleme myself but no success so you will not help okey and its not a shorten lived rom belive me this is my first time building and ineed help from experienced developers like nitin and you if you don't wanna help me its okey but don't broken me
nitin.chobhe said:
You should add the github links for ROM source, your device, kernel, vendor trees.
Nitin
Click to expand...
Click to collapse
sir here you go
Rom source :
https://github.com/AOSiP
Device tree code :
https://github.com/RinGooDz/AOSIP-Device-Tree-for-shamu.git
Kernel tree is from Nitrogen os without any changes : https://github.com/nitrogen-os-devices/android_kernel_moto_shamu.git
Vendor tree is also from Nitrogen os without any changes :
https://github.com/nitrogen-os-devices/android_vendor_motorola.git
AmirHRC said:
you also start from zero bro okey so don't be so serious like this everyone start like this and android development doesn't need a lot of code I managed to build the rom but its stuck at the bootanimation i tried to fix the probleme myself but no success so you will not help okey and its not a shorten life rom belive me this is my first time building and ineed help from experienced developers like nitin and you if you don't wanna help me its okey but don't broken me
Click to expand...
Click to collapse
First of all I'm not your bro!
Of course I started at zero. I started as translator for CyanogenMod. Then I learned how to compile stuff, do smaller changes, maintain a already brought up ROM and then finally port Android 8 and 9 for shamu.
I had a lot of people which I could ask for help, but usually I only asked them if I didn't make any progress for days.
You on the other hand try to start on 100 % that is not very promissing to be a success.
I said short lived ROM because I saw a lot of people come and go and most of them were not very persitent.
I never said that I don't want to help at all. I usually try to be helpfull ( I guess some of the other devs know it), but I want to see some efforts from the one who is asking for help.
Elektroschmock said:
First of all I'm not your bro!
Of course I started at zero. I started as translator for CyanogenMod. Then I learned how to compile stuff, do smaller changes, maintain a already brought up ROM and then finally port Android 8 and 9 for shamu.
I had a lot of people which I could ask for help, but usually I only asked them if I didn't make any progress for days.
You on the other hand try to start on 100 % that is not very promissing to be a success.
I said short lived ROM because I saw a lot of people come and go and most of them were not very persitent.
I never said that I don't want to help at all. I usually try to be helpfull ( I guess some of the other devs know it), but I want to see some efforts from the one who is asking for help.
Click to expand...
Click to collapse
i did efforts the past 3 day I was trying to fix this but no success if I didn't try I will not tell you help me and you don't want its okey just don't tell me you cant or something like this its my first time and I did what ican to fix this but no success
AmirHRC said:
i did efforts the past 3 day I was trying to fix this but no success if I didn't try I will not tell you help me and you don't want its okey just don't tell me you cant or something like this if you can help me help me its my first time and I did what ican to fix this but no success
Click to expand...
Click to collapse
Okay then one Protip from me: You are using a Android O device tree. You are lacking about 50 of my commits to be even bootable on P.
Starting around here: https://github.com/LineageOS/androi...=ff0d752ee1ef7bf3eeed3393475a5451c1e13a62+104
Elektroschmock said:
Okay then one Protip from me: You are using a Android O device tree. You are lacking about 50 of my commits to be even bootable on P.
Starting around here: https://github.com/LineageOS/androi...=ff0d752ee1ef7bf3eeed3393475a5451c1e13a62+104
Click to expand...
Click to collapse
thank you sir I will start working now thank you very much
sorry for all this I'm still learning and learning from developer like you its amazing
hello every one no luck with aosip but ifinished building havoc os 9.0 the build run smooth but I have some problems when try to make call the phone make system ui reboot iwill try to fix it now if someone can help please help
and also the rom compiled without bootanimation
so give me some time iwill post it as soon as i fix those
Elektroschmock said:
Okay then one Protip from me: You are using a Android O device tree. You are lacking about 50 of my commits to be even bootable on P.
Starting around here: https://github.com/LineageOS/androi...=ff0d752ee1ef7bf3eeed3393475a5451c1e13a62+104
Click to expand...
Click to collapse
i tried what you sad but no chance i think the probleme is from aosip source itried every thing every soulution but no boot
so itried building havoc os 9.0 the phone booted fine from the first try and its run smooth only some problems I will try to fix them
I like aosip, so I build aosip for nexus 4/5 6P.
Yesterday, shamu was also build and booted.
What is the reason you start with o-tree?
Elektroschmock said:
First of all I'm not your bro!
Of course I started at zero. I started as translator for CyanogenMod. Then I learned how to compile stuff, do smaller changes, maintain a already brought up ROM and then finally port Android 8 and 9 for shamu.
I had a lot of people which I could ask for help, but usually I only asked them if I didn't make any progress for days.
You on the other hand try to start on 100 % that is not very promissing to be a success.
I said short lived ROM because I saw a lot of people come and go and most of them were not very persitent.
I never said that I don't want to help at all. I usually try to be helpfull ( I guess some of the other devs know it), but I want to see some efforts from the one who is asking for help.
Click to expand...
Click to collapse
sir can you help me with this
iam trying to make call the phone reboot here is the logcat :
https://gist.github.com/RinGooDz/48c745ad5eb5b3bae541ccd165c535d1
ithink the probleme is here how ican fix it please sir
07-01 21:48:15.210 665 665 I Telecom : DefaultDialerCache: Refreshing default dialer for user 0: now com.android.dialer: [email protected]
07-01 21:48:15.211 665 665 I Telecom : MissedCallNotifierImpl: reloadAfterBootComplete: user=0: [email protected]
07-01 21:48:15.310 665 665 I Telecom : PhoneAccountRegistrar: SimCallManager queried, returning: null: [email protected]
07-01 21:48:15.452 1594 1594 I TelecomFramework: : Carrier-config changed, checking for phone account updates.
07-01 21:48:15.493 1594 1594 I TelecomFramework: AccountEntry: reRegisterPstnPhoneAccount: subId: 1 - no change
07-01 21:48:15.519 1594 1594 I TelecomFramework: PstnIncomingCallNotifier: Unregistering: Handler (com.android.internal.telephony.GsmCdmaPhone) {53a6f62}
07-01 21:48:15.605 665 1786 I Telecom : PhoneAccountRegistrar: Modify account: [ComponentInfo{com.android.phone/com.android.services.telephony.TelephonyConnectionService}, ***, UserHandle{0}]: [email protected]
07-01 21:48:15.611 1594 1594 I TelecomFramework: AccountEntry: Registered phoneAccount: [[ ] PhoneAccount: ComponentInfo{com.android.phone/com.android.services.telephony.TelephonyConnectionService}, ***, UserHandle{0} Capabilities: CallProvider MultiUser PlaceEmerg SimSub Audio Routes: BESW Schemes: tel voicemail Extras: Bundle[{android.telecom.extra.SUPPORTS_VIDEO_CALLING_FALLBACK=true}] GroupId: ***] with handle: ComponentInfo{com.android.phone/com.android.services.telephony.TelephonyConnectionService}, ***, UserHandle{0}
07-01 21:48:15.612 1594 1594 I TelecomFramework: PstnIncomingCallNotifier: Registering: Handler (com.android.internal.telephony.GsmCdmaPhone) {53a6f62}
07-01 21:48:15.625 1594 1594 I TelecomFramework: PstnPhoneCapabilitiesNotifier: handleVideoCapabilitesChanged. Video capability - false
07-01 21:48:15.647 665 1835 I Telecom : PhoneAccountRegistrar: Modify account: [ComponentInfo{com.android.phone/com.android.services.telephony.TelephonyConnectionService}, ***, UserHandle{0}]: [email protected]
Caused by: java.lang.ClassNotFoundException: Didn't find class "org.codeaurora.internal.IExtTelephony" on path: DexPathList[[zip file "/system/priv-app/Telecom/Telecom.apk"],nativeLibraryDirectories=[/system/priv-app/Telecom/lib/arm, /system/lib, /system/vendor/lib, /system/lib, /system/vendor/lib]]
voidz777 said:
I like aosip, so I build aosip for nexus 4/5 6P.
Yesterday, shamu was also build and booted.
What is the reason you start with o-tree?
Click to expand...
Click to collapse
Where is Nexus 4 build?
Nitin
nitin.chobhe said:
Where is Nexus 4 build?
Nitin
Click to expand...
Click to collapse
It's sleeping deep in my heart.
...Oh, what a mess. The screen shot is flat.
voidz777 said:
It's sleeping deep in my heart.
...Oh, what a mess. The screen shot is flat.
Click to expand...
Click to collapse
Nice, may be you can share it
Nitin