Related
incubus26jc has released a Froyo (Androis 2.2) port for the vogue. This *might* as always work on nike. If you want to give it a shot, here's the original thread:
http://forum.xda-developers.com/showthread.php?t=712310
Btw: The vogue community is way faster than g1, still waiting for froyo to hit my device
i have try it, it works for me, and the same bug, difficult to receive call, no bluetooth, no camera. And with the newest kernel - broken sound. Can you fix that kernel?can we ask dzo to fix kernel for Nike user?is there a way to make bluetooth and camera working?
Yeah, lagloose already informed me about the kernel problems. I don't have much time coding atm, but i gave it a quick shot yesterday.
Havent tested it yet as my touch dual is somewhere in a drawer at home and i have to look for it .
If you want to give it a try and report back if it works:
http://84.23.71.227/kerneloftheday/zImage_audiotest
BTW, nice to hear that the rom is working.
€: In principle it should be possible to get the cam and bt to work. I tried to play around with BT, but I was not able to get it working. Must have missed something...
looks like you are the only one who can compile Nike kernel, just contact dzo, he doesn't have time to did it for Nike user, he asked me to find someone who know some C and linux box to make the kernel. maybe we can asked some tips from him and applied it on Nike kernel?
i think the first thing is to make receiving call working, it seems like when using android, it is difficult to make our phone ring when receiving call and why this made we can't use our phone with android.
hope you can spend sometime for this problem, i'm very appreciated your work for Nike communities... thank you very much
testing...
Mblaser, I tested the kernel, touchscren not work!
OK, I will try again tomorrow. Messed up my kernel autobuild and have to fix it first...
sound working for me, it's back to normal again although in highest volume level it is still too loud and the sound is a little broken, but seems find in lower sound level, maybe a little more adjustment to that will make it better.
and just find another thing, i have my receiving call problem solved even i'm activated vibrate function. for now hope mblaster and maxxd01 can make bluetooth and camera working in zimage kernel.
here is what i did:
1. update newest kernel using mblaster kernel with audio bug free from http://forum.xda-developers.com/showpost.php?p=7021840&postcount=3
2. using phone prioritizer from http://forum.xda-developers.com/showthread.php?t=558822
this will make android a much more usability
leonardoaraujo said:
Mblaser, I tested the kernel, touchscren not work!
Click to expand...
Click to collapse
Are you on nike100?
€: Kernel service up again with audio patch included. Hope verything works now. Niki100 version is also patched now, touchscreen problems seem to be vibration related on niki100 (thats why there is a vibration free version especially for theat phone).
http://84.23.71.227/kerneloftheday/
Sent from my Htcclay's SuperBad G1 using XDA App
€€: Let this thread sink, there is another one on the same topic here: http://forum.xda-developers.com/showthread.php?p=7037314#post7037314
If you have something to say, go and post there!
I noticed there was no active development that was trying to get the standard AOSP build working, which I really would like to use as my day to day ROM....so I decided to give it a shot. Feel free to help
I use the Ninphetamine kernel and a clockwork recovery initramfs. The initramfs has been altered and will not boot with other ones. This is because of a missing socket that the older init.rc doesn't make.
I'll be using the next post to describe what I'm working on and update it with any useful info I find.
Currently it's in an unusable state, here's where it stands:
Working
Making calls
SMS
Audio
Internet (Data Connection)
Note: When you open browser, it will crash because google's home page try's to use location services, you need to navigate away quickly in order for it not to crash.
Proximity Sensor
Internal Storage
microSD Storage
Vibration
Camera
USB Transfer with Internal Storage
Untested
Other Sensors
TV Out (doubtful)
Not Working (yet)
WiFi (don't even turn this on, it will reboot endlessly) <-- working on it
Camcorder
Bluetooth
GPS
USB Transfer with microSD (not a huge priority)
I know that cyanogenmod is pretty darn close to AOSP and that I'm duplicating work, but I'm doing it anyways.
If you want to try it out:
Binaries:
CWM Kernel Zip
CWM AOSP Zip
Note: Obviously you need to wipe.
Sources:
https://github.com/nemasu/
Working on WiFi
no notes yet
nemasu said:
I noticed there was no active development that was trying to get the standard AOSP build working, which I really would like to use as my day to day ROM....so I decided to give it a shot. Feel free to help
Click to expand...
Click to collapse
AdamG has made devnull (http://forum.xda-developers.com/showthread.php?t=1183063&highlight=devnull) which is basicly the AOSP build. Some stuff not working though as the CM7 team has not managed to get audio over bluetooth working.
He has also started the Oxygen development. The oxygen thread is here: http://www.forums.acsyndicate.net/showthread.php/1591-ROM-AOSP-GRJ90-2.3.5-Oxygen-v2.2.1
Good to hear others working on this too, hope you manage to get bluetooth audio issue sorted and perhaps help other AOSP / CM7 devs with that issue.
Pume said:
AdamG has made devnull (http://forum.xda-developers.com/showthread.php?t=1183063&highlight=devnull) which is basicly the AOSP build. Some stuff not working though as the CM7 team has not managed to get audio over bluetooth working.
He has also started the Oxygen development. The oxygen thread is here: http://www.forums.acsyndicate.net/showthread.php/1591-ROM-AOSP-GRJ90-2.3.5-Oxygen-v2.2.1
Good to hear others working on this too, hope you manage to get bluetooth audio issue sorted and perhaps help other AOSP / CM7 devs with that issue.
Click to expand...
Click to collapse
Ah, yeah, I forgot about that one. I'll be leaving it completely stock AOSP though (when it works well anyways). Might speed things up for me a bit. I am doing this as a sort of hobby too, interesting to learn how it works.
EDIT: It WILL speed things up a great deal....DevNull did some great work.
search for the Oxygen ROM on google.
it's a rom for SGS2 where everything works, and it's only AOSP.
http://forum.oxygen.im/index.php
All the same, great work mate, we need more AOSP ROM's, since AdamG has taken a break due to personal reasons it's nice for another dev to take the helm.
Good luck mate, all the best.
nesquix said:
search for the Oxygen ROM on google.
it's a rom for SGS2 where everything works, and it's only AOSP.
http://forum.oxygen.im/index.php
Click to expand...
Click to collapse
Does A2DP work on Oxygen?
Sent from my CM7 powered SGS2
This xda members...
AdamG did great work yes but it does not preclude to new AOSP roms.
Keep your respected work.
Edit: If AdamG had taken a break, maybe you should think to fork devnull. This speeds up work and you can focus another thinks etc A2DP and tvout. Its open source
I have been using CM7 as well as Devnull/Oxygen and I felt Oxygen was very stable, while CM7 26 was the most stable for me while 31 made my me turn back to Oxygen.
My sincere request, kindly take over from where Adam left Will be a great boon for us!
bluheart said:
I have been using CM7 as well as Devnull/Oxygen and I felt Oxygen was very stable, while CM7 26 was the most stable for me while 31 made my me turn back to Oxygen.
My sincere request, kindly take over from where Adam left Will be a great boon for us!
Click to expand...
Click to collapse
Agree......
Sent from my GT-I9100 using Tapatalk
Keep up the good work!
Nice work buddy
I turn my back for 1 day and you're nearly done! Keep it up
does it have a aosp lockscreen only?
Always nice to see more AOSP love will be keeping an eye on this, good luck man no wifi would be a dealbreaker for me ATM..
wliu88 said:
does it have a aosp lockscreen only?
Click to expand...
Click to collapse
yup, I've added nothing to it, pure aosp.
Hi! I'm trying to reproduce this compilation but no success. It stucks with a lot of libs errors. Any idea? I'm using a little modified device configuration from android_device_samsung_galaxys2.
Sent from my GT-I9100 using XDA App
Has anyone got two way voice recording working on any of the ICS releases, whether a MOD or a 3rd Party app?
I tried a couple (killer mobile and call recorder) but no luck.
same here. call recorder always worked 100%
Anyone? Still can't find one that will work....aaarrrggg.
I would like to know too. I heard Samsung has removed the necessary call recording libraries in ICS. Hope that is not true.
afaik it will work soon, becuase the ics kernel sources are published today. that will grant many developers to fix everything which cant be fixed before. afaik the call recording problem inlcuded!
Looking forward to this. I loved that on GB. There is a tutorial @ "Original Android Development" category (for GB), maybe someone can start from there to make it work on ICS?
-Aeth.
aethery said:
Looking forward to this. I loved that on GB. There is a tutorial @ "Original Android Development" category (for GB), maybe someone can start from there to make it work on ICS?
-Aeth.
Click to expand...
Click to collapse
Where's the tutorial?
1+
Before I use CallRecorder but now it does not work ok
me too. that was very useful as it recorded automatically
I can confirm, call recorders does not work on ICS.
I tried almost all available from the market, but no success.
I need it too
Sent from my GT-I9100
This seems to be an useful thread - http://forum.xda-developers.com/showthread.php?t=1482721 - this actually points to a easy way of getting call recording functionality back!
Here's my understanding from the thread. Basically there are three files in /system/lib that are used for call recording API -
libaudioflinger.so
libaudio.so
libaudiopolicy.so
(It's interesting to note that out of these, only the first is there in ICS.)
If we copy the files from 2.3.6, and replace/add the files, there's a good chance that we will get back call recording. Now to get these files... does anybody have the older version, or know how to extract these files from the ROMs?
SOLVED XD - Need to know if it's reliable
Hi,
I have tried "Auto Call Recorder" (free) and seems to work ok.
Without any patchs or modifications on the rom it works ok recording from mic (depending on you it could be wnought or not).
QUESTION 1:
Someone could tell us if this program is realiable? (I mean, if we can trust in it).
Because it have several permissions that I'm not sure it should have or if it's neccesary.
It has 100.000 - 500.000 installations and 4 star score
How can we be sure if this program is not spying us?
RECORDING WITH API (not mic)
Here http://forum.xda-developers.com/showthread.php?t=1551353 I have found a thread where there are two ICS libs (different from the GB ones) that sould fix the problem and should allow to record from API, so we could get clear and loud sound.
Files are audio.primary.exynos4.so & audio_policy.exynos4.so in /system/lib/hw
Files can be downloaded from http://www.mediafire.com/?r2wgv821w1uutzd or from http://forum.xda-developers.com/attachment.php?attachmentid=955906&d=1332235902 (both are binary same)
QUESTION 2:
Again reliability.
Someone could tell us if this libs are realiable? (I mean, if we can trust in it).
I have downloaded "ZSLPE" that is supposed to have call recording and this libs are the same that the original in XXLPQ, and are different of the downloable ones that I say before (supposely patched).
If ZSLPE have call recording, why libs are the same that XXLPQ?
Where are this "patched" libs from?
Again the same question, are this "patched" libs reliable?
Perhaps I could be some paranoid, but I don't want a spy on my phone or something worse, and I want to be sure that all my phone conversations (or any other personal data) are not sent to anyone.
Probably is stupid to think that anyone could be interested in my bored conversations, but those are mine...
Greetings
^ Thanks given
For security concern, you may want to try out LBE Privacy Guard... I use it. It can help you to deny certain permissions for any program which you think has no business asking for the permission.
You may question that program more though, as it asks for a lot more permissions in return for the power!
Personally, I would trust the libraries and the auto call recorder - the permissions it asks seem legit. I checked the hack works with Total Recall too, so if you feel more comfortable you could use that.
hirak99 said:
I checked the hack works with Total Recall too, so if you feel more comfortable you could use that.
Click to expand...
Click to collapse
Could you explain what you mean by this I not sure I understand.
Thanks to everyone who has been responding it looks like we might not be too far away from call recording on ICS. WooHoo!
OzBoy1 said:
Could you explain what you mean by this I not sure I understand.
Thanks to everyone who has been responding it looks like we might not be too far away from call recording on ICS. WooHoo!
Click to expand...
Click to collapse
I installed the two .so files mentioned in this thread into /system/lib/hw -
http://forum.xda-developers.com/showthread.php?t=1551353&page=2
After a while this worked for me, for both Total Recall and Auto Call Recorder. I have DXLP7 with CFRoot LP7 kernel.
Alternatively, according to the same thread, in ZSLPE call recording works from start.
Let me know if that helps, or I can answer any other questions to get it working for you.
i installed resurrection rom 1.0 and when i tested it, it works. have to press record yourself mind.
tommo123 said:
i installed resurrection rom 1.0 and when i tested it, it works. have to press record yourself mind.
Click to expand...
Click to collapse
in phone settings - extend settings, you can set it automatic for incomming and outgoing calls. works like a charm here and records both sides (i'm using resurrection rom 1.0 too)
elroy944 said:
in phone settings - extend settings, you can set it automatic for incomming and outgoing calls. works like a charm here and records both sides (i'm using resurrection rom 1.0 too)
Click to expand...
Click to collapse
Does it work with bluetooth?
I can confirm that the call recording on Resurrection rom 1.0 works flawlessly.
This is for developers only. No builds will be posted in this thread.
https://github.com/CM10DNA
Any valid development related discussion can be posted here. Please no posts that aren't directly related to development (i.e. comments, thanks, etc.).
I thought I would share an update on how this very experimental code-base is doing.
The code is running again (much of yesterday it was crashing on startup).
I have been running dirty flashing from my CM 10.1 build. It seems like that was safe to do so. I tried doing a clean flash this morning but sadly, my clean flash seems to have broken cell service. No phone or data. Restoring my cm 10.1 backup of data to the same install fixed it. Strange. (This included the change pushed this morning that updates the version of the apns file).
Superuser is now working but may be a little flaky. For example, on my clean install Titanium Backup couldn't acquire root access until after I rebooted.
Camera is still not working. It says "failed to connect to camera". I haven't looked at it at all, but there is a massive commit in the M7 kernel pulling source from the HTC One Google Edition for the camera.
Overall, I'm finding it's either completely broken or working very well. I think that the cellular network issue is going to get resolved upstream. I am afraid that we might be on our own for the camera.
crpalmer said:
I thought I would share an update on how this very experimental code-base is doing.
The code is running again (much of yesterday it was crashing on startup).
I have been running dirty flashing from my CM 10.1 build. It seems like that was safe to do so. I tried doing a clean flash this morning but sadly, my clean flash seems to have broken cell service. No phone or data. Restoring my cm 10.1 backup of data to the same install fixed it. Strange. (This included the change pushed this morning that updates the version of the apns file).
Superuser is now working but may be a little flaky. For example, on my clean install Titanium Backup couldn't acquire root access until after I rebooted.
Camera is still not working. It says "failed to connect to camera". I haven't looked at it at all, but there is a massive commit in the M7 kernel pulling source from the HTC One Google Edition for the camera.
Overall, I'm finding it's either completely broken or working very well. I think that the cellular network issue is going to get resolved upstream. I am afraid that we might be on our own for the camera.
Click to expand...
Click to collapse
https://github.com/CyanogenMod/andr...mmit/ec27077d6497c66f52488126ef6b181ef3fbed0d
seems cm has stopped camera building throughout probably prepping for the focal merge
edit: idk if m7 has cam working but it hasn't been detected as a bug
"Current bugs (they are known):
SMS sending will not work (receiving works)
Dialer sub-submenu FC's the dialer
Keyboard FC's when gesture swiping"
Not sure how much this helps. But the m7 kernel recently got its camera code updated with the Google edition. http://review.cyanogenmod.org/#/c/46164/
With that so. They are able to use the 4.2 libs http://review.cyanogenmod.org/#/c/46299/
Flyhalf205 said:
Not sure how much this helps. But the m7 kernel recently got its camera code updated with the Google edition. http://review.cyanogenmod.org/#/c/46164/
With that so. They are able to use the 4.2 libs http://review.cyanogenmod.org/#/c/46299/
Click to expand...
Click to collapse
we'd probably have to merge their whole drivers/media/video/msm and use their camera binaries at least that's how it works with sense if you want to use their 4.2.2 cam libs
JoelZ9614 said:
we'd probably have to merge their whole drivers/media/video/msm and use their camera binaries at least that's how it works with sense if you want to use their 4.2.2 cam libs
Click to expand...
Click to collapse
And their commit conflicts all over the place which is going to make it hard to cherry pick it. This was the commit I referred to earlier today.
On the plus side, the ril issue looks like it will get resolved for us. There is a commit out there for Samsung hardware that adds a couple of RIL events that look like they have been added.
crpalmer said:
And their commit conflicts all over the place which is going to make it hard to cherry pick it. This was the commit I referred to earlier today.
On the plus side, the ril issue looks like it will get resolved for us. There is a commit out there for Samsung hardware that adds a couple of RIL events that look like they have been added.
Click to expand...
Click to collapse
What about the commit introducing the HTCCDMAQualcommRIL?
Sent from my HTC6435LVW using xda app-developers app
times_infinity said:
What about the commit introducing the HTCCDMAQualcommRIL?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Which commit?
crpalmer said:
Which commit?
Click to expand...
Click to collapse
http://review.cyanogenmod.org/#/c/45607/
Hope it helps.
Sent from my HTC6435LVW using xda app-developers app
I'll take a look at the radio stuff tomorrow. I have a couple ideas.
Deck got data working on the m7 (Sprint), check the commits or wait until tomorrow if he hasn't pushed them yet
Sent from my buttered S3
chad0989 said:
I'll take a look at the radio stuff tomorrow. I have a couple ideas.
Click to expand...
Click to collapse
To be clear, it is working fine for me if I dirty flash. I have been running 10.2 builds for 48 hours everywhere from strong wifi to bad 3G in the middle of a forest.
It's only breaking if I do a factory reset before flashing a build. That's why my guess was that it was related to this event being missing:
cyanogenmod.org/#/c/46280/1/libril/ril.cpp
(around line 2240) and that a similar change was going to be required to our libril. My inclination would be to wait and see what happens with the M7 builds (which it sounds are coming along) and see if it just magically fixes itself for us....
Edited to add: sending of text messages wasn't working but looks like they were supposed fixed last night (I haven't built it to test it yet)
crpalmer said:
And their commit conflicts all over the place which is going to make it hard to cherry pick it. This was the commit I referred to earlier today.
On the plus side, the ril issue looks like it will get resolved for us. There is a commit out there for Samsung hardware that adds a couple of RIL events that look like they have been added.
Click to expand...
Click to collapse
mm actually now that i look at it drivers/media/video/msm has been left basically untouched in our source updating to what the m7 has shouldn't be too much of a problem
JoelZ9614 said:
mm actually now that i look at it drivers/media/video/msm has been left basically untouched in our source updating to what the m7 has shouldn't be too much of a problem
Click to expand...
Click to collapse
I tried a cherry-pick before and it looked very bad. But, actually, a lot of it looks like it could be related to the comments that HTC strips from the source when the release that I added back (because it makes it easier to patch from all non-HTC sources).
If you want to take a crack at this, try doing this before cherry-picking their commit:
git show c81741a8337c2342d856ffeac0cc087452729290 drivers/media/video/msm include/media/msm_camera.h | patch -p1 -R
That will strip all the comments back out again and get rid of all those conflicts. The conflicts then look very simple (outside of arch/arm/mach-msm, which is where it gets much harder).
crpalmer said:
I tried a cherry-pick before and it looked very bad. But, actually, a lot of it looks like it could be related to the comments that HTC strips from the source when the release that I added back (because it makes it easier to patch from all non-HTC sources).
If you want to take a crack at this, try doing this before cherry-picking their commit:
git show c81741a8337c2342d856ffeac0cc087452729290 drivers/media/video/msm include/media/msm_camera.h | patch -p1 -R
That will strip all the comments back out again and get rid of all those conflicts. The conflicts then look very simple (outside of arch/arm/mach-msm, which is where it gets much harder).
Click to expand...
Click to collapse
the board-monarudo-camera.c doesn't need to be updated, at least i didn't update it in my m7 kernel port
but i can't seem to get the kernel to build
drivers/gpu/msm/adreno_snapshot.c: In function 'snapshot_rb':
drivers/gpu/msm/adreno_snapshot.c:628: sorry, unimplemented: inlining failed in call to 'parse_ib': recursive inlining
drivers/gpu/msm/adreno_snapshot.c:588: sorry, unimplemented: called from here
make[3]: *** [drivers/gpu/msm/adreno_snapshot.o] Error 1
make[2]: *** [drivers/gpu/msm] Error 2
make[1]: *** [drivers/gpu] Error 2
make[1]: *** Waiting for unfinished jobs....
i don't believe it's related to any edits i made tho heres my commit https://github.com/Joelz9614/android_kernel_htc_dlx/commit/daa90f2bf8e64a8ad6f4f497ca412bc0a77ab7ef
JoelZ9614 said:
the board-monarudo-camera.c doesn't need to be updated, at least i didn't update it in my m7 kernel port
but i can't seem to get the kernel to build
drivers/gpu/msm/adreno_snapshot.c: In function 'snapshot_rb':
drivers/gpu/msm/adreno_snapshot.c:628: sorry, unimplemented: inlining failed in call to 'parse_ib': recursive inlining
drivers/gpu/msm/adreno_snapshot.c:588: sorry, unimplemented: called from here
make[3]: *** [drivers/gpu/msm/adreno_snapshot.o] Error 1
make[2]: *** [drivers/gpu/msm] Error 2
make[1]: *** [drivers/gpu] Error 2
make[1]: *** Waiting for unfinished jobs....
i don't believe it's related to any edits i made tho heres my commit https://github.com/Joelz9614/android_kernel_htc_dlx/commit/daa90f2bf8e64a8ad6f4f497ca412bc0a77ab7ef
Click to expand...
Click to collapse
Searching in the browser doesn't have any matches for adreno_snapshot...
Maybe try git checkout -b tmp HEAD~1 and make sure that builds?
Looks like CM just merged an updated audio HAL along with the legacy HAL, both of which incorrectly detect our device for now. Building with a fix now and if all is well I'll submit upstream.
Edit: It's going to cause a bunch of routing issues again also until some other stuff gets merged in. Best to just revert their change for now for builds.
chad0989 said:
Looks like CM just merged an updated audio HAL along with the legacy HAL, both of which incorrectly detect our device for now. Building with a fix now and if all is well I'll submit upstream.
Edit: It's going to cause a bunch of routing issues again also until some other stuff gets merged in. Best to just revert their change for now for builds.
Click to expand...
Click to collapse
Aside from the routing issues, this may already be fixed for us thanks to the m7:
http://review.cyanogenmod.org/#/c/46473/
@chad0989, FYI, I reverted the commit to use legacy alsa early this morning and haven't noticed any problems (play music on Bluetooth, voice calls with and without wired headset) using that build.
You may want to give it a try and see if you're ready to revert it.
Edit: actually, I just noticed that they had also enabled legacy audio in msm8960-common but since reverted that. So, I guess I was still running the legacy mode...
crpalmer said:
@chad0989, FYI, I reverted the commit to use legacy alsa early this morning and haven't noticed any problems (play music on Bluetooth, voice calls with and without wired headset) using that build.
You may want to give it a try and see if you're ready to revert it.
Edit: actually, I just noticed that they had also enabled legacy audio in msm8960-common but since reverted that. So, I guess I was still running the legacy mode...
Click to expand...
Click to collapse
They aren't allowing new HAL to build yet (see https://github.com/CyanogenMod/android_hardware_qcom_audio-caf/blob/cm-10.2/Android.mk) But we will need that flag when they allow the new HAL to build. I added it preemptively to hopefully avoid breakage. The issue was that the legacy HAL they pushed hadn't included some changes for our CSD client and platform detection. Looking at what was committed last night/today it should work now though.
Deleted
Cool. Downloading and will give it a go in a second. Thanks
Enjoy, I put a bit of effort trying to get this off the ground. Both ROM and COS Mod.
Help please..
Does anyone know a way to change the way the ROM builds? Cause the way it builds now there's no /system folder in the zip, just .bin files for the system instead. If I knew how to make it build the old way with it still there, I so would. Odexed too if possible
Edit: Might have figured these 2 things out.. . Will report results
Added to OnePlus One index thread:
[INDEX] OnePlus One
Gonna give it a try
Thanks, but I'd wait a minute.. I'm updating the ROM link as I type this lol. Tests were successful and R2 is great so far
a little too late, but i'll clean flash the new build (No Problem)
New build may have some unknown error. Google Play Services keeps crashing and I have no clue why...
By DEX_PREOPT =true , does it mean the ROM is fully Odexed ?
Partially so far, just frameworks. But working on rest now.And trying to figure out this Google Play Services bug. Only seems to happen after allowing location in the regular browser (not Chrome).
Keep it up ! Will try it when the play services bug is resolved. I'm attracted towards Odexed ROMs as they are better in terms of performance and battery life
R3 is up, link updated too . Finished the odexing, fixed play services issue. Good to go
Good now man
@ZX64
Can you upload it to mediafire also?
Google Services seems to be working fine now. Only had one CRASH witch was Hangout. Once it restarted, made a few text and calls. Seems to be working fine now
Okay. Yeah, I haven't got any errors yet. Being watchful. Seems great though. It got 48891 with Antutu after my restore of like 70+ apps and a reboot. Which COS usually tanks to 47000- after that. So I'm satisfied for now till I learn how to get Uber GCC 5.1 working. Not sure how all these other people do it. Nobody tells me anything when I ask, like its some big secret or something.
Sorry but no mediafire, can I ask why? I'll try to hook you up somehow if I can. I'm all about user experience, and actually listening to what people want rather than building and saying "take it or leave it". Just cause I'm inexperienced doesn't mean I don't have some skills to bring to the table.
Came here thinking I could simply do like any other Linux community, jump in, learn as I go, with a huge community to help anytime I need help learning new things, till together something wonderful is created in the end
Builds going on hold till I find a way to use Uber 5.x toolchains.
I need more build flags, and 4.8 isn't allowing any of the flags used to use on UnityROM-2.
Any help would be seriously amazing at this point
Ask varund7726 help you his rom has Uber 5.2 in this thread here http://forum.xda-developers.com/oneplus-one/development/rom-resurrection-remix-lp-5-2-0-t2971715