Since Spyke555 is busy, I updated cm10.1 with his last device tree.
You can download from http://dualhoki.vim.hu/bubor/dev/10.1/cm-10.1-20131024-UNOFFICIAL-i927.zip
Please read http://forum.xda-developers.com/showthread.php?t=2217288
It has same issues. Cm has security bugfix, and I want to keep cm up to date.
- Gps was fixed.
20131025: update to cm 10.1.3, increaes dalvik.vm.heapsize, android_packages_app_settings at b1755aad3d3ad2ac0e72297a6b4b60031d15ff69
20150826: cm security update
issue
same as other cm 10.1
settings -> about crash
ghost call: please try litekernel
Updated kernel here: http://dualhoki.vim.hu/bubor/dev/11.0/tegra-reserved-192mb-kernel-only-oldone.zip with lowered tegra reserved memory ( more usable memory)
Litekernel found here
Androide3 said:
Home long press not work
Sent from my SGH-I927 using xda premium
Click to expand...
Click to collapse
settings -> system -> hardware keys -> enable custom actions (check) and home key (long press) set to Recent app switcher
And you may set app switch key to voice search, so mic key will work as voice search.
Didn't have time to test everything but gave it a quick spin but noticed something right away... Couldn't download from playstore. Gave some error about couldn't find information.
Had to go back to spykes last version which is dd, will try to play more later. for reference I don't have any playstore issue after restore.
Neuntoter said:
Didn't have time to test everything but gave it a quick spin but noticed something right away... Couldn't download from playstore. Gave some error about couldn't find information.
Had to go back to spykes last version which is dd, will try to play more later. for reference I don't have any playstore issue after restore.
Click to expand...
Click to collapse
Was that clean install?
I can install app from play store.
bubor said:
Was that clean install?
I can install app from play store.
Click to expand...
Click to collapse
The only thing I didn't wipe was the sdcard.
I will give it a better shake later today. Were you using tonyg-nonneon gaps?
Neuntoter said:
The only thing I didn't wipe was the sdcard.
I will give it a better shake later today. Were you using tonyg-nonneon gaps?
Click to expand...
Click to collapse
yes
bubor said:
Since Spyke555 is busy, I updated cm10.1 with his last device tree.
You can download from http://dualhoki.vim.hu/bubor/cm-10.1-20130725-UNOFFICIAL-i927.zip
Please read http://forum.xda-developers.com/showthread.php?t=2217288
Click to expand...
Click to collapse
kudos bubor !
Unfortunately it seems the same issues that Kick is having with calls is present here as well so it's definitely seems to be something from CM. I haven't had anyone try to call me but I made a test call and was unable to end the call.
m1batt1 said:
Unfortunately it seems the same issues that Kick is having with calls is present here as well so it's definitely seems to be something from CM. I haven't had anyone try to call me but I made a test call and was unable to end the call.
Click to expand...
Click to collapse
please try this:
http://dualhoki.vim.hu/bubor/cm-10.1-20130726-UNOFFICIAL-i927.zip
ITs use opensource libril. Please feedback ASAP
bubor said:
please try this:
http://dualhoki.vim.hu/bubor/cm-10.1-20130726-UNOFFICIAL-i927.zip
ITs use opensource libril. Please feedback ASAP
Click to expand...
Click to collapse
I just got to work and won't be able to test until later tonight but I'll check it out and let you know.
Sent from my SGH-I927 using xda app-developers app
bubor said:
please try this:
http://dualhoki.vim.hu/bubor/cm-10.1-20130726-UNOFFICIAL-i927.zip
ITs use opensource libril. Please feedback ASAP
Click to expand...
Click to collapse
i tried it and calls work normally, i can end a call and i can recieve calls with no problem!
bubor said:
please try this:
http://dualhoki.vim.hu/bubor/cm-10.1-20130726-UNOFFICIAL-i927.zip
ITs use opensource libril. Please feedback ASAP
Click to expand...
Click to collapse
Hey! I'm at work currently but got chance to test it so here it goes what I found.
Calls: ok. I did 2 calls, receive 2 calls, did 1 outgoing call and put speaker, and receive 1 call and also test with speaker. So far all calls had audio.
Skype, and this is interesting. I tested from the glide to my work skype account, and in the glide the audio is still broken:
- Calling from glide to pc: I could hear myself ok ON the PC (so lets say the other side could hear me), but not FROM the pc, I heard it was all all deep and slow (nothing new to me there). I could even turn on the video call and it worked.
- Calling from pc to glide, skype in the glide just dies and restarts.
I'm sorry I cannot test more, I'm at work. I was using CM 10.1 RC2 from spyke555 and dirty flashed this one (just cleared cache and dalvik).
Bubor, if you can think a protocol for testing specific things (for example 1-test X and note results, 2-test Y and note resulted, after all tests report back to forum with results) somehting like that that would be equal among all that we are testing and might give you insight of the problems or if you need to test just 1 particulare thing, well, for that thing.
Keep it up people, let's give the devs what they need, tests, reports, results, they give us their time doing this, we must at least do the same!
Bubor, its CM10.1.2 o 10.1
Sent from my SGH-I927 using xda app-developers app
ugoPS said:
Bubor, its CM10.1.2 o 10.1
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
10.1.2, you can check in about phone -> "view changelog"
Skype doesnt work. This build should be same as before, same bugs.
Okay. Did full wipe of sdcard and all, now no issues with play store.
Now I have never had voice search work with hot word detection, and that is still the case. Am I just lame or is this the way it should be. I had heard people talk about it working before.
Calls work. Both directions 4 times each tested. can hang up etc.
Unless there is something else supposedly fixed I guess it works for me.
How did you include the kernel? Just put the zip in the kernel/samsung/i927 folder?
Also are you still using the proprietary vendor files from The Covenant?
I know libril is a library for radio access but can you help me understand which one we need and how to include it in the build?
Thanks for any help you can provide still working on my first build after hours of downloading cm repo.
Neuntoter said:
How did you include the kernel? Just put the zip in the kernel/samsung/i927 folder?
Also are you still using the proprietary vendor files from The Covenant?
I know libril is a library for radio access but can you help me understand which one we need and how to include it in the build?
Thanks for any help you can provide still working on my first build after hours of downloading cm repo.
Click to expand...
Click to collapse
this device tree including kernel binary and modules. It would fail to build, if you include kernel source with this device tree.
Both device and vendor files you can found http://dualhoki.vim.hu/bubor/dev/cm-10.1-20130726-UNOFFICIAL-i927.tgz
You need one more thing that is https://github.com/CyanogenMod/android_hardware_samsung (just change _ to / for correct path)
bubor said:
this device tree including kernel binary and modules. It would fail to build, if you include kernel source with this device tree.
Both device and vendor files you can found http://dualhoki.vim.hu/bubor/dev/cm-10.1-20130726-UNOFFICIAL-i927.tgz
You need one more thing that is https://github.com/CyanogenMod/android_hardware_samsung (just change _ to / for correct path)
Click to expand...
Click to collapse
When you say kernel binary you mean the zip I download from kickass right? Are you saying I just put that in the kernel/samsung/i927 folder and it will automatically be included?
Just to clarify.
Get rid of device tree I got from spyke555's GIT and use the ones from your tgz. Now I assume I still put them in device/samsung/i927 and vendor/samsung/i927 right?
for the https://github.com/CyanogenMod/android_hardware_samsung
Do I just git clone that into the root? Or where should I be putting this?
Sorry for all the questions but I want to make sure I learn this and am a help later on.
Neuntoter said:
When you say kernel binary you mean the zip I download from kickass right? Are you saying I just put that in the kernel/samsung/i927 folder and it will automatically be included?
Just to clarify.
Get rid of device tree I got from spyke555's GIT and use the ones from your tgz. Now I assume I still put them in device/samsung/i927 and vendor/samsung/i927 right?
for the https://github.com/CyanogenMod/android_hardware_samsung
Do I just git clone that into the root? Or where should I be putting this?
Sorry for all the questions but I want to make sure I learn this and am a help later on.
Click to expand...
Click to collapse
Depend what is in your boardconfig.mk, if it has prebuild things, you would not put kernel source, but put kernel binary.
TARGET_PREBUILT_KERNEL := device/samsung/i927/prebuilt/kernel
TARGET_PREBUILT_RECOVERY := device/samsung/i927/prebuilt/recovery.img
If you use kernel source, it would be:
TARGET_KERNEL_SOURCE := kernel/samsung/i927
TARGET_KERNEL_CONFIG := tegra_bose_defconfig
Where keren source path, and the other is the defconfig what is in kernel/samsung/i927/arch/arm/configs
When you change _ to / in android_hardware_samsung you get android/hardware/samsung where android is the dir where you start, so you put to hardware/samsung. With command
git clone https://github.com/CyanogenMod/android_hardware_samsung hardware/samsung
Click to expand...
Click to collapse
Or you can put to the manifest, so repo sync will update to you.
If you wish, I could put whole directory to somewhere, but it would be something like 30giga.
Thank you Bubor! Couldn't of done it without you!
It appears to be building. I guess I won't know for sure until it is done.
bubor said:
Since Spyke555 is busy, I updated cm10.1 with his last device tree.
You can download from http://dualhoki.vim.hu/bubor/cm-10.1-20130726-UNOFFICIAL-i927.zip
Please read http://forum.xda-developers.com/showthread.php?t=2217288
It has same issues. Cm has security bugfix, and I want to keep cm up to date.
Last month I tried to fix tinyalsa, what fix most sound issue ( except bt calls). I'll keep trying.
Click to expand...
Click to collapse
Bubor, local forum users say that GPS is finally fixed in your build. I can confirm that, now GPS status and toolbox shows much more sattelites than previous CM versions. Thanx for that!
Related
i have pushed the board files to my github to compile a fully working kernel for the GSM Hero. i dont own the device, but Behnaam has been working with me testing and such. anyhow everything works. the link to my source can be found below:
GoDmOdE-KeRnEl-SoUrCe
anyhow enjoy i do this for the community and ask for nothing but in return. Devs have at it!!!
Behnaam already beat you to the punch, link.
gu1dry said:
Behnaam already beat you to the punch, link.
Click to expand...
Click to collapse
i seen but i can update this one plus i guess i forgot to add two files . btw they are there now and it will compile for sure. (i just did it) enjoy
will it say no more huge battery drain ?
Quick and dirty compile by me in boot.img format (too tired to hack an update.zip together)
Credit to: Benocharm, and well everyone else who worked on this project... i just compiled it lol
EDIT: Had a lapse and forgot to compile a new wlan module... will reupload after school today
Cant post links yet sooo h**p://w w w .mega upload. c o m/ ? d = 724NZ7Q1
** = tt
remove spaces
Method One Flash: (For those with unlocked SPL)
fastboot flash boot newBoot.img
fastboot reboot
Method Two Flash:
adb push boot.img /sdcard
adb shell
cat /dev/zero > /dev/mtd/mtd2
- write: No space left on device [this is ok, you can ignore]
flash_image boot /sdcard/boot.img
reboot your phone
zjr8 said:
Quick and dirty compile by me in boot.img format (too tired to hack an update.zip together)
Credit to: Benocharm, and well everyone else who worked on this project... i just compiled it lol
Cant post links yet sooo h**p://w w w .mega upload. c o m/ ? d = 724NZ7Q1
** = tt
remove spaces
Method One Flash: (For those with unlocked SPL)
fastboot flash boot newBoot.img
fastboot reboot
Method Two Flash:
adb push boot.img /sdcard
adb shell
cat /dev/zero > /dev/mtd/mtd2
- write: No space left on device [this is ok, you can ignore]
flash_image boot /sdcard/boot.img
reboot your phone
Click to expand...
Click to collapse
Here ya go mate
http://www.megaupload.com/?d=724NZ7Q1
Are the video drivers included?
MerXury13 said:
Are the video drivers included?
Click to expand...
Click to collapse
I think that's very basic that they check it .
I'm more curious about other things that are not so obvious while testing:
volume keys while sleeping, battery usage, g-sensor, correct behavior of the audio jack (audio switches to jack instead of speaker), etc...
'gsm long text > 160 chars' issues can't have anything to do with the kernel used as I see it. That's something of the messaging app and / or the radio RIL used.
Hmm, new kernel to play with... might be the push I needed to try building my own android stuff to learn
Am I missing something with regards to the wlan module sources? Didn't see them so far...
Or am I being stupid (highly likely)
Are the video drivers included?
Click to expand...
Click to collapse
I think that's very basic that they check it .
I'm more curious about other things that are not so obvious while testing:
volume keys while sleeping, battery usage, g-sensor, correct behavior of the audio jack (audio switches to jack instead of speaker), etc...
'gsm long text > 160 chars' issues can't have anything to do with the kernel used as I see it. That's something of the messaging app and / or the radio RIL used.
Hmm, new kernel to play with... might be the push I needed to try building my own android stuff to learn
Click to expand...
Click to collapse
I asked 'cause in the cronos Rom, the developer said that he excluded the Video drivers to f**k up the other devs ...what a jerk
MerXury13 said:
I asked 'cause in the cronos Rom, the developer said that he excluded the Video drivers to f**k up the other devs ...what a jerk
Click to expand...
Click to collapse
dude, he only did that on his 'OC' version. The normal 'stable' version has them... reading is an artform
I asked 'cause in the cronos Rom, the developer said that he excluded the Video drivers to f**k up the other devs ...what a jerk
Click to expand...
Click to collapse
dude, he only did that on his 'OC' version. The normal 'stable' version has them... reading is an artform
Click to expand...
Click to collapse
It's too early for me^^ sorry
dipje said:
dude, he only did that on his 'OC' version. The normal 'stable' version has them... reading is an artform
Click to expand...
Click to collapse
The normal 'stable' version of his ROM is built on the same test kernal that every other 2.1 ROM is built on.
MerXury13 said:
I asked 'cause in the cronos Rom, the developer said that he excluded the Video drivers to f**k up the other devs ...what a jerk
Click to expand...
Click to collapse
Again... getting boring
Can someone please compile this one with overclock patch?I have no idea how to compile from source else I would do it
l0st.prophet said:
The normal 'stable' version of his ROM is built on the same test kernal that every other 2.1 ROM is built on.
Click to expand...
Click to collapse
Hence it got video drivers
Can anyone point me in the direction of a good write up on how to build a boot.img from this git repo please?im using ubuntu 10.4
so can we use this kernel on the vanilla roms?
anon2122 said:
Am I missing something with regards to the wlan module sources? Didn't see them so far...
Or am I being stupid (highly likely)
Click to expand...
Click to collapse
Do you have the latest commit? I believe initially there were some missing files. I know when I grabbed the source the first time i had wlan drive compile issues
I applied this to both cronos rom and to superhero rom and both got really sluggish after installing it (I used the boot.img posted among the first posts).
This is a nightly of TeamChopsticks' CM9 for the hercules. It is in no way official, therefore, you should not go reporting bugs to CyanogenMod, rather to me.
Requirements
Blaze MODIFIED ICS Radio (Thanks TheDerekJay!)
Click to expand...
Click to collapse
How to install
1. NANDROID BACKUP YOUR CURRENT ROM! I will not be responsible if you start a world war because you didn't backup your current ROM!
2. Update radio to Blaze MODIFIED ICS Radio if you haven't already.
3. Flash DARKSIDE.SUPER.WIPE
4. Install CM9 zip from the SDCard
5. Install Gapps zip from the SDCard
6. Flash DARKSIDE.CACHE.WIPE
7. Reboot. Let it sit for 10 minutes after first boot.
How to upgrade from previous version of THIS ROM
1. NANDROID BACKUP YOUR CURRENT ROM! I will not be responsible if you start a world war because you didn't backup your current ROM!
2. Update radio to Blaze MODIFIED ICS Radio if you haven't already.
3. Format /system (Mounts and Storage > Format /system)
4. Install CM9 zip from the SDCard
5. Install Gapps zip from the SDCard
6. ONLY IF YOU ARE ON NON-TOUCH CWM RECOVERY: Flash DARKSIDE.CACHE.WIPE
7. ONLY IF YOU ARE ON TOUCH CWM RECOVERY: Format /cache (Mounts and Storage > Format /cache)
8. Reboot. Let it sit for 10 minutes after first boot.
Click to expand...
Click to collapse
Thanks to
TeamChopsticks
CyanogenMod Team
mikeyman77
- Mr. X -
Click to expand...
Click to collapse
Downloads
Nightlies (Download the latest one): http://goo.im/devs/KonstantinKeller
MD5Sum: On download page
Gapps: http://goo.im/gapps/gapps-ics-20120429-signed.zip
MD5Sum: 7c524e1e078164f681e0aa6753180b2c
Click to expand...
Click to collapse
Donations aren't required, but are extremely appreciated.
Whats working
Wifi
Data
Audio
Calls
NFC
Videos
Camera
Camcorder
Etc...
Bugs
Low call volume on the other end
Camcorder effects do not work.
Sometimes the touchscreen locks up and ignores input. See workaround in FAQs.
To-Do List
Anything else I come up with
Changelog
Nightly Build 4
Fixed homescreen size bug
Nightly Build 3
New Build
Nightly Build 2
Goo-Manager and ROM Manager update support!
Call echo fixed!
Nightly Build 1
Initial Release
Click to expand...
Click to collapse
FAQs
Why is my phone not mounting on my computer?
Open Settings, go to Storage. Press menu, USB Computer connection. Uncheck 'Media device (MTP)' and check 'Mass Storage'
Sometimes my touchscreen locks up and ignores input. What do I do?
Put your palm on the whole screen while it is on and move your palm around. That should reset the touchscreen controller and work again. Or you can reboot.
Is there call echo?
No.
Whats the difference between this CM9 and TeamChopsticks' CM9?
This one is built from source every single day, so think of this as a nightly. Plus, I will be adding more features to it, and it won't be just CM9.
Building from Source
Setting up your Build Environment
Follow the instructions here to set up your build environment.
Get Google's repo script from the "Installing Repo" section of this page. (Don't go past the "Installing Repo" section though.)
Downloading the Source
Create a directory in which you will be doing all the work (or a work directory) and cd into it. (Example: "mkdir ~/android; cd ~/android")
Initialize the work directory to download the source from github: repo init -u git://github.com/CyanogenMod/android.git -b ics
Create a local manifest for the android vendor blobs: nano .repo/local_manifest.xml
Copy and paste this into the file:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/samsung/hercules" name="CyanogenMod/android_device_samsung_hercules" />
<project path="device/samsung/msm8660-common" name="CyanogenMod/android_device_samsung_msm8660-common" />
<project path="vendor/samsung/hercules" name="TeamChopsticks/android_vendor_samsung_hercules" />
</manifest>
Save and exit
Building for Hercules
IF THIS IS A REBUILD OF THE SOURCE, type "make clobber" first to erase all the files from the previous build!
. build/envsetup.sh (Notice its period, space, build/envsetup.sh)
./vendor/cm/get-prebuilts
CM_EXTRAVERSION=my_custom_build CM_SNAPSHOT=1 brunch cm_hercules-userdebug
difference between this and the other one is?
Sent from my ASUS Transformer Pad TF300T using XDA
new ion? said:
difference between this and the other one is?
Sent from my ASUS Transformer Pad TF300T using XDA
Click to expand...
Click to collapse
Different bugs, and I'm gonna build this one everyday, so it's more of a nightly.
new ion? said:
difference between this and the other one is?
Sent from my ASUS Transformer Pad TF300T using XDA
Click to expand...
Click to collapse
+1
bkrill said:
+1
Click to expand...
Click to collapse
Already answered. Check the FAQs.
It seems the T989 has its own Young Ace Dev (like M0D1441 for the Skyrocket)!!
Good luck to ya, man!
SupaKid said:
It seems the T989 has its own Young Ace Dev (like M0D1441 for the Skyrocket)!!
Good luck to ya, man!
Click to expand...
Click to collapse
Thanks bro!
Im still waiting for the first "call echo" question lol
bryancotton84 said:
Im still waiting for the first "call echo" question lol
Click to expand...
Click to collapse
Going off the way you said it.... Its there?
Sent from my SGH-T989 using XDA
new ion? said:
Going off the way you said it.... Its there?
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
Just tested...Me calling another cell, no issues, crystal clear for the receiver...same person calling me had some issue, just wasnt as clear...
bryancotton84 said:
Just tested...Me calling another cell, no issues, crystal clear for the receiver...same person calling me had some issue, just wasnt as clear...
Click to expand...
Click to collapse
On this ROM? So, it booted fine I see. Is everything working? Sorry for asking, I just don't have my phone with me currently
KonstantinKeller said:
On this ROM? So, it booted fine I see. Is everything working? Sorry for asking, I just don't have my phone with me currently
Click to expand...
Click to collapse
Yep, got everything set up how I like it with no issues other than the previously mentioned
EDIT: One thing I have noticed with this ROM and the Team Chopsticks is there is a slight delay from turning the screen on, to the screen actually coming on...really isnt an issue just something ive noticed
bryancotton84 said:
Yep, got everything set up how I like it with no issues other than the previously mentioned
EDIT: One thing I have noticed with this ROM and the Team Chopsticks is there is a slight delay from turning the screen on, to the screen actually coming on...really isnt an issue just something ive noticed
Click to expand...
Click to collapse
Alright thanks. So Wifi, Data, and all of that works? Awesome.
KonstantinKeller said:
Alright thanks. So Wifi, Data, and all of that works? Awesome.
Click to expand...
Click to collapse
well maybe data isnt working so great, ive done speed test several times and its only showing 0.06 down and ive flashed two separate radios
bryancotton84 said:
well maybe data isnt working so great, ive done speed test several times and its only showing 0.06 down and ive flashed two separate radios
Click to expand...
Click to collapse
I'll check it out. Thanks
backlit keys working?
Call Echo & Roaming
I keep getting this "Roaming" data and it's slow as hell. Is there another radio or anything I can do to get regular signal? About call echo, it's hard to say because I've been on this ROM for about 10 minutes. I called my brother and he said he was echoing but he is also on AOKP which is messy when it comes to calls. Everything is super fast and runs amazing. And yes, backlight keys work.
So, i started building CM10.1 using androidarmv6 sources which are known for working with msm7x27a. I modified my device folder and it builds.
Any help would be apreciated.
If anyone is intrested in development please join #Lproj on freenode to exchange ideas
Current status:
- It boots to GUI [L5&L7]
- Camera works [L5&L7]
- ril partially works (no outgoing calls)
- sdcard works
TODO:
- outgoing calls
- video rec
- audio routing in calls (l7 only?)
And the thank you award goes to the following: @PecanCM @cybojenix @adfad666
device folders
here speaks of cm10.1, but I tried it and I can not figure out if there are any differences or not :/ :http://forum.android.com.pl/f759/cm10-avatar-rom-extreme-291710/
michelemascia7 said:
here speaks of cm10.1, but I tried it and I can not figure out if there are any differences or not :/ :http://forum.android.com.pl/f759/cm10-avatar-rom-extreme-291710/
Click to expand...
Click to collapse
Go to Settings > System > About phone and make a screenshot please.
I want to see if it really is CM10.1
CM10.1
It is not clear cm10.1 just my version of the beta, made by me cm10.1 and avatar rom from nexus 4 and firmware LG optimus G.
My version cm10.1 not publish.
crinca15 said:
Go to Settings > System > About phone and make a screenshot please.
I want to see if it really is CM10.1
Click to expand...
Click to collapse
I have now flashed the pac rom of Metallica, and can not do a screenshot :/
evidently it is not 10.1 as confirmed @szymel0
I just tryed RC7 of it! Works nice. I jumped from PACman Rom to Avatar CM10.1 without wipe cache or data...
But do I need CM10.1 gapps ?
crinca15 said:
I just tryed RC7 of it! Works nice. I jumped from PACman Rom to Avatar CM10.1 without wipe cache or data...
But do I need CM10.1 gapps ?
Click to expand...
Click to collapse
i had flashed cm10 gapps but careful not to go off topic :silly:
Please stay ontopic
michelemascia7 said:
i had flashed cm10 gapps but careful not to go off topic :silly:
Click to expand...
Click to collapse
https://drive.google.com/folderview?id=0B2Yt4LYuF0UuNDdEUXZYSmtxTFU&usp=sharing
RC9 Exists (Just to say, sry for off topic, had to say it)
EDIT : And I think you should ask some experience users of this, because they can help you (or not xD), I can´t help you, Since I entered on xda, I just did a ROM for galaxy gio, so a little of experience.
friends, i didn't understand one thing, i can flash Avatar EXTREME RC7 CM 10.1 , for my LG P700? or not is for our phone this rom? question by the read in this topic.
sorry for offs topic
your logcat say you are using normal qcom_display folder not legacy one and that's created this problem and which kernel you are using ? because
E/hwcomposer( 4290): FATAL:vsync_loop:not able to open file:/sys/class/graphics/fb0/vsync_event, No such file or directory
PecanCM said:
your logcat say you are using normal qcom_display folder not legacy one and that's created this problem and which kernel you are using ? because
E/hwcomposer( 4290): FATAL:vsync_loop:not able to open file:/sys/class/graphics/fb0/vsync_event, No such file or directory
Click to expand...
Click to collapse
I use qcom legacy from android armv6 and still get this error. Also I tried to use a branch from legacy droid that user adfad666 pointed me to and still getting the same error. I use stock 3.4.0 cm10 kernel. Are there any modifications I should make to kernel?
second logcat http://pastebin.com/6JGw1fvy
Sent from my LG-P700 using xda app-developers app
Maybe a problem with the drivers adreno 200?
I am not a developer (yet) but maybe try porting files from a device silmilar to ours and start modifying from there ??
Good luck on your work and hope you succeed
Sent from my LG-P700 using xda app-developers app
tudorsirb said:
I use qcom legacy from android armv6 and still get this error. Also I tried to use a branch from legacy droid that user adfad666 pointed me to and still getting the same error. I use stock 3.4.0 cm10 kernel. Are there any modifications I should make to kernel?
second logcat http://pastebin.com/6JGw1fvy
Sent from my LG-P700 using xda app-developers app
Click to expand...
Click to collapse
so 1st logcat with adfad666 display folder and 2nd logcat with androidarmv6 display folder right ? and i asked because it's strange you using stock cm10 kernel and vsync_event node not created
PecanCM said:
so 1st logcat with adfad666 display folder and 2nd logcat with androidarmv6 display folder right ? and i asked because it's strange you using stock cm10 kernel and vsync_event node not created
Click to expand...
Click to collapse
First is from a bad build where I forgot to add legacy. Second is from adfad's repo. with legacy I get the same errors.
EDIT: I use adreno blobs from cm10 should i use different ones for cm10? i also tried referece blobs from Qualcomm
Sent from my LG-P700 using xda app-developers app
tudorsirb said:
If anyone is intrested in development please join #p700 on freenode to exchange ideas
Click to expand...
Click to collapse
is this channel not being used then?
this morning I uploaded my device config for l5 which seemed to solve the egl error, however I haven't tried it since the last kernel, so don't even know if it boots (I was messing with the boot.img from alpha firmware, and source of the l3 ii)
hope this helps
cybojenix said:
is this channel not being used then?
this morning I uploaded my device config for l5 which seemed to solve the egl error, however I haven't tried it since the last kernel, so don't even know if it boots (I was messing with the boot.img from alpha firmware, and source of the l3 ii)
hope this helps
Click to expand...
Click to collapse
thanks, i fixed egl with it Now i'm stuck at boot animation with some weird errors.
tudorsirb you are my god!! I pray to you and hope cm10.1 will be finnished after the summer vacations!!
Sent from my LG-P700 using xda premium
ubuntuh said:
tudorsirb you are my god!! I pray to you and hope cm10.1 will be work after the summer vacations!!
Sent from my LG-P700 using xda premium
Click to expand...
Click to collapse
Thank cybojenix beacuse i'm getting loads of help from him
For those who prefer open source builds, rather than "Factory Images", here is a zip which is a stock, AOSP 4.3 build, straight from source. Why post this when anyone could make it? Well, it seems Google messed up their binary drivers, so it took me a little while to fix them, and fix the problems and get the ROM booting (they put the wrong mali GLES driver in their blob package).
Anyway, I have fixed that, and made it build successfully, so without futher ado, an AOSP (no google proprietary apps etc) build of 4.3 for the Nexus 10. The fixed vendor blobs are available at https://github.com/pulser/vendor_samsung_manta for anyone wanting to build themselves, and all can be verified, as they came from the "Factory Image" of 4.3 for the Nexus 10.
This is a pure AOSP build, there is no boot animation or any other "Google" things - just a plain, pure, AOSP build.
Enjoy, and this can be rooted using Chainfire's current 4.3 root method using SuperSU, which is detailed at https://plus.google.com/+Chainfire/posts/WqS2E9kkN1L
Feel free to use, share, re-use, distribute, copy, paste, mirror, ignore, root, tweak, patch or mod. I am not like certain individuals who go ZOMG NO MIRRORS PLEASE... Go on, mirror, make a torrent if you want, and share it if anyone actually cares about this
Tested:
Wi-Fi
Bluetooth
GPS
Auto rotation
Accelermeter
Magnetic Field Sensor
Brightness Sensor (and Autobrightness)
Barometer
Seemingly not working:
Proximity sensor (not detected, but apparently has one)
Download:
http://goo.im/devs/pulser/Nexus10
Hmmm...I'm co cerned what you said about they put the wrong Mali driver in. What does this effect for those of us who flashed the stock image from the website?..
Sent from my SCH-I535 using xda app-developers app
duarian said:
Hmmm...I'm co cerned what you said about they put the wrong Mali driver in. What does this effect for those of us who flashed the stock image from the website?..
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Stock image isn't the AOSP?
I am not worrying.
Thanks OP.
duarian said:
Hmmm...I'm co cerned what you said about they put the wrong Mali driver in. What does this effect for those of us who flashed the stock image from the website?..
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Nothing to worry about. I took the RIGHT driver from the factory image (stock image).
The AOSP release they made had wrong blobs, I rectified it with the correct files from the stock image.
I missed a blob:
https://github.com/pulser/vendor_samsung_manta/commit/4c534c24407a163bc16bfa24cb769aef7ab9ebd3
Push to /system/vendor/lib/
pulser_g2 said:
I missed a blob:
https://github.com/pulser/vendor_samsung_manta/commit/4c534c24407a163bc16bfa24cb769aef7ab9ebd3
Push to /system/vendor/lib/
Click to expand...
Click to collapse
How do we download the file/blob please?
Never downloaded anything from Github before...
pulser_g2 said:
For those who prefer open source builds, rather than "Factory Images", here is a zip which is a stock, AOSP 4.3 build, straight from source. Why post this when anyone could make it? Well, it seems Google messed up their binary drivers, so it took me a little while to fix them, and fix the problems and get the ROM booting (they put the wrong mali GLES driver in their blob package).
Anyway, I have fixed that, and made it build successfully, so without futher ado, an AOSP (no google proprietary apps etc) build of 4.3 for the Nexus 10. The fixed vendor blobs are available at https://github.com/pulser/vendor_samsung_manta for anyone wanting to build themselves, and all can be verified, as they came from the "Factory Image" of 4.3 for the Nexus 10.
This is a pure AOSP build, there is no boot animation or any other "Google" things - just a plain, pure, AOSP build.
Enjoy, and this can be rooted using Chainfire's current 4.3 root method using SuperSU, which is detailed at https://plus.google.com/+Chainfire/posts/WqS2E9kkN1L
Feel free to use, share, re-use, distribute, copy, paste, mirror, ignore, root, tweak, patch or mod. I am not like certain individuals who go ZOMG NO MIRRORS PLEASE... Go on, mirror, make a torrent if you want, and share it if anyone actually cares about this
Tested:
Wi-Fi
Bluetooth
GPS
Auto rotation
Accelermeter
Magnetic Field Sensor
Brightness Sensor (and Autobrightness)
Barometer
Seemingly not working:
Proximity sensor (not detected, but apparently has one)
Download:
http://goo.im/devs/pulser/Nexus10
Click to expand...
Click to collapse
Is this why the latest version supported for manta is 4.2.2r1 (according to this) while everything else is 4.3xx?
Explains why I can't get a flashable build.
This is why I stick to factory images.
ridobe said:
Is this why the latest version supported for manta is 4.2.2r1 (according to this) while everything else is 4.3xx?
Explains why I can't get a flashable build.
Click to expand...
Click to collapse
It may well be, but the factory image is available.
But some of us don't want GApps, and don't want binary parts (save for the necessary evil of drivers), which is where AOSP builds come in.
pulser_g2 said:
It may well be, but the factory image is available.
But some of us don't want GApps, and don't want binary parts (save for the necessary evil of drivers), which is where AOSP builds come in.
Click to expand...
Click to collapse
Thanks. I like to build for myself but couldn't figure out why I couldn't flash successfully. Upon further investigation it appears that it is not supported (yet) in aosp. I'm running the factory images for now instead. However, this evening I'm going to flash this.
I just want to make sure. This wont wipe my internal hard drive. First time i flashed the new 4.2 i lost everything and cant backup anything as of now because i am outta town the whole summer.. Plz if anybody can confirm
Sent from my Nexus 10 using Tapatalk HD
BabyHuey said:
I just want to make sure. This wont wipe my internal hard drive. First time i flashed the new 4.2 i lost everything and cant backup anything as of now because i am outta town the whole summer.. Plz if anybody can confirm
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
I am not aware of anything to deliberately wipe /data, but I strongly suggest you don't flash this, unless you are willing to lose things? Why? because I didn't test every possible situation that could come up. I also didn't CHECK that /data remained...
So perhaps take the OTA (if you're on stock)? Or just hang off? It's nothing hugely special in my opinion.
pulser_g2 said:
I also didn't CHECK that /data remained...
Click to expand...
Click to collapse
It does, I flashed it.
Would still like to know how to get those missing blobs...
stonebear said:
It does, I flashed it.
Would still like to know how to get those missing blobs...
Click to expand...
Click to collapse
So nothing will be wiped?
Sent from my Nexus 10 using Tapatalk HD
BabyHuey said:
So nothing will be wiped?
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
My data remained, but I would be concerned if you took a chance on my say so and something went wrong. I was ok but maybe you wouldn't be for some reason.
Sent from my Nexus 7 using Tapatalk 4 Beta
stonebear said:
It does, I flashed it.
Would still like to know how to get those missing blobs...
Click to expand...
Click to collapse
Which ones? The blobs are in the github link and came from the factory image. I'm not aware of any missing ones.
pulser_g2 said:
Which ones? The blobs are in the github link and came from the factory image. I'm not aware of any missing ones.
Click to expand...
Click to collapse
I don't know how to download them. Are they downloadable?
I suppose if I could understand the page I would know which ones to take from the factory image...noob, sorry.
Is it just "libRSDriverArm.so"?
http://d-h.st/aPi
4.3 gapps
Sent from my AOSP on Manta using Tapatalk HD
Thanks pulser_g2 for adding the correct binary blobs! Glad I'm not completely insane like I thought I was, I too noticed that Google had forgotten to provide the correct graphics driver binaries so I tried building 4.3 with the 4.2.2 graphics binaries and it not surprisingly didn't boot past the Google logo. Glad we could get this fixed :good:.
stonebear said:
I don't know how to download them. Are they downloadable?
I suppose if I could understand the page I would know which ones to take from the factory image...noob, sorry.
Is it just "libRSDriverArm.so"?
Click to expand...
Click to collapse
Sure, that is the only "blob" I am aware I forgot. The N10 supposedly supports Bluetooth 4 (LE), but I have no idea how to test it, as I don't have any Bluetooth 4 LE devices. Can anyone test that? I will update the system.img today for you to make it easier It was only one blob I missed, and it only affects using front facing camera I believe.
Rom based on this: https://forum.xda-developers.com/elephone-p9000/development/rom-aokp-nougat-t3690278
Full credits go to the AOKP team who made the rom for P9000.
To use on P9000 Lite you may need CWM 3.0.2.8 and you have to restore the backup zip provided in the link.
Features:
- Same as P9000 AOKP rom.
- Gapps (Micro) come preinstalled.
Warnings:
- The unpacked rom uses up to 5200MB, so make sure you got free space!
- Put the rom backup on an SD Card, not on internal memory.
- Fingerprint options make the settings app crash (Obviously).
Bugs:
- The rom occupies about 20GB because of a bug.
- Charging seems to be painfully slow. (If someone could fix this, it would be really awesome.)
Installation:
You have to put the folder from the zip in TWRP\BACKUPS.
It should appear and then you should be able to see the rom and install it.
Download Links:
http://aftermath-studio.go.ro/IBOVHQ49DEAML78T.zip
http://aftermath-studio.go.ro:8080/Upload/IBOVHQ49DEAML78T.zip - Edit: I also added a torrent in the attachments.
(Please post to mirrors and post comments with the mirrors, and I'll update the original post)
Good luck!
Update:
For my phone, it charged the battery a bit, or so it seems, and then it kept going down.
Not sure what the bug is, at least for now.
So keep this in mind while downloading.
Any contribution is greatly appreciated.
xnd_bogdan said:
Update:
For my phone, it charged the battery a bit, or so it seems, and then it kept going down.
Not sure what the bug is, at least for now.
So keep this in mind while downloading.
Any contribution is greatly appreciated.
Click to expand...
Click to collapse
ATM I can only point you to CONFIG_MTK_PUMP_EXPRESS_(PLUS_)SUPPORT.
Did you set the following in devconfig?
Code:
CONFIG_MTK_PUMP_EXPRESS_SUPPORT=y
CONFIG_MTK_PUMP_EXPRESS_PLUS_SUPPORT=y
Tarkness said:
ATM I can only point you to CONFIG_MTK_PUMP_EXPRESS_(PLUS_)SUPPORT.
Did you set the following in devconfig?
Click to expand...
Click to collapse
he ported the rom, doesnt seem like he build it
Ruben Craveiro said:
he ported the rom, doesnt seem like he build it
Click to expand...
Click to collapse
Yup.
That's what I did
xnd_bogdan said:
Yup.
That's what I did
Click to expand...
Click to collapse
you need to change more modules and change some stuff on boot.img i think on the file init.rc on boot.img to allow charging
Ruben Craveiro said:
you need to change more modules and change some stuff on boot.img i think on the file init.rc on boot.img to allow charging
Click to expand...
Click to collapse
I'll definitely try doing that but for now I took a break, since finals are coming.
If somebody fixes it before I get to have some free time, that would be even better to be honest.
xnd_bogdan said:
I'll definitely try doing that but for now I took a break, since finals are coming.
If somebody fixes it before I get to have some free time, that would be even better to be honest.
Click to expand...
Click to collapse
i doubt that will happend, i dont think many people use the lite version, me in particular use the normal version, so i cant really fix it.
Do we know if anyone fixed it?
Sent from my Redmi 5 Plus using Tapatalk
Hi!
Anybody fixed the problems?
Hello.
I was going to continue porting this but unfortunately my phone failed so I was forced to buy a new one.
I'm afraid I can't work on this anymore, as I no longer have a p9000 lite