As i promised I have been working into this build , finally got ti working properly and to be used as a daily driver. As for now I´m testing ( I don't have much time ) if you want to try it and give feedback I´ll try to repair all the bugs.I think everything is working at least for me ( 256gb/6gb ram ). I don't have much time to write a proper post so I will give you the mega link ( soon upload to androidfilehost ) . I promise to merge all the updates on the base code.
Download Linkhttps://mega.nz/#!dbozEBpb!kNG-ea8AYNovLEiAf-s_SDreC9xYAsHTpuIa2rxVIKM
Credits
Big thanks to Marchetto ,BitO, CAF devs , Papps , all of you for downloading and testing and Me for spending 1 month with the rom hehe. Nothing more to say , just enjoy AOSP and pure Android. Best wishes and happy week.
Edit: NFC Not working ( Working on it , sorry : ( )
Nice..downloading and excited to try this out
rhong said:
Nice..downloading and excited to try this out
Click to expand...
Click to collapse
Enjoy !! And if you wish report bugs!!! Thanks for downloading ^-^
YazumiWuHung said:
Enjoy !! And if you wish report bugs!!! Thanks for downloading ^-^
Click to expand...
Click to collapse
Installed and running smoothly. The difference between PA by Bito and this is that this one is purely aosp .
Bugs encountered while replying is that chrome fc but when reopen it runs OK again. That's it for now.
Thanks dev!
Great!! Is proximity sensor working..? I have it pending in PA...
Can you share links to device tree sources, please?
Big thx for your work @YazumiWuHung !
I would love to have a ROM that properly nails the proximity sensor.
MrColdbird said:
I would love to have a ROM that properly nails the proximity sensor.
Click to expand...
Click to collapse
Even on stock ROMs there are the problems we have with our builds. And i'm fairly sure that several cases the users have are not making the situatrion better.
BitOBSessiOn said:
Great!! Is proximity sensor working..? I have it pending in PA...
Can you share links to device tree sources, please?
Big thx for your work @YazumiWuHung !
Click to expand...
Click to collapse
Yeah its working , at first it didn't but It does now. Brightness too ( Auto too ) , I have tried to make all work .
When I come back to Hong Kong ( tomorrow ) I´ll update the post with all the info and make it good looking .
Thanks i'll try tomorrow night
The problem isn't whether the sensor works or not, it's about whether it works reliably.
My proximity sensor sometimes does work, sometimes it doesn't, with the latter being the more common case, forcing me to manually turn the screen off during a call as to not hang up on the other side with my ear.
MrColdbird said:
The problem isn't whether the sensor works or not, it's about whether it works reliably.
My proximity sensor sometimes does work, sometimes it doesn't, with the latter being the more common case, forcing me to manually turn the screen off during a call as to not hang up on the other side with my ear.
Click to expand...
Click to collapse
Ah, really
The only time where the proximity was working reliably was with my first devicetree for the mix that was based on the marchmallow blobs. Since the switch to oss sound + nougat blobs it isn't working 100% for several users. As said, if you browse the China dev based ROM threads you could find several reports stating the same issues you describe. The logical conclussion is, the blobs Xiaomi provides are the problem, if you have problems like that with the stock based ROMs, too.
Anyway there are several cases on the market that make the proximity more unreliable too. I've tested and owned many cases and found two producing 100% the same issue and one killing the proximity 100%.
But you're right, the main issue is for sure the driver software.
Seems good, anyway to swap back and recent button
james1089 said:
Seems good, anyway to swap back and recent button
Click to expand...
Click to collapse
Probably need Xposed as this is pure aosp, no bells and whistles.
Sent from my MI MIX using XDA-Developers Legacy app
pappschlumpf said:
Ah, really
The only time where the proximity was working reliably was with my first devicetree for the mix that was based on the marchmallow blobs. Since the switch to oss sound + nougat blobs it isn't working 100% for several users. As said, if you browse the China dev based ROM threads you could find several reports stating the same issues you describe. The logical conclussion is, the blobs Xiaomi provides are the problem, if you have problems like that with the stock based ROMs, too.
Anyway there are several cases on the market that make the proximity more unreliable too. I've tested and owned many cases and found two producing 100% the same issue and one killing the proximity 100%.
But you're right, the main issue is for sure the driver software.
Click to expand...
Click to collapse
On ViperOs the proximity sensor has worked perfect and I have never had any issues with the sensor
Ultraman666 said:
On ViperOs the proximity sensor has worked perfect and I have never had any issues with the sensor
Click to expand...
Click to collapse
Yea viper and screwd, then other problems appeared down the line.
james1089 said:
Yea viper and screwd, then other problems appeared down the line.
Click to expand...
Click to collapse
I have no issues with anything on ViperOs...
I am going to download this and give it a try
Sent from my Viper MI MIX using Tapatalk
Ultraman666 said:
I have no issues with anything on ViperOs...
I am going to download this and give it a try
Click to expand...
Click to collapse
No Bluetooth streaming on screwd ROM.
Fine for Bluetooth calls though.
YazumiWuHung said:
Edit: NFC Not working ( Working on it , sorry : ( )
Click to expand...
Click to collapse
Any update on NFC fix?
Cheers
Enjoying the ROM
is there a reup link for this?
Related
@P4R
(I created this thread because I'm a new member, I can't answer on the original one. (and usually I don't post on XDA but this ROM got all my attention )
I'm using CM11s port 1.4 on my Nexus 5 this is what I noticed : (clean flash)
- Battery is consumed on sleep, no CPU wake up
- Lockscreen's battery percent doesn't match the system one
- Proximity sensor does't work for checking when to wake up or not
- QuickBoot : the phone goes on this mode, no way to boot again unless I use Power+Vol buttons
- HDR mode should work on this build (1.4) but it doesn't, I have to flash the fix for 1.2 and lower
OnePlus said there're fixes for battery drain in the way...(OTA but when...)
I really liked this ROM, even with less features than the original one ... Knock code in native would be great ! with ElementalX.
the issues are expected, its a port. by nature, ports will be buggy and have issues. but who knows, maybe they will eventually fix them, or not, the next android version will probably be out long before everything works on the port.
One thing to remember is that this is not a port. It's CyanogenMod M8 with added apps and some minor build.prop edits. Any problems you experience are CM problems.
TheLastSidekick said:
One thing to remember is that this is not a port. It's CyanogenMod M8 with added apps and some minor build.prop edits. Any problems you experience are CM problems.
Click to expand...
Click to collapse
the ports not a port? lmao
simms22 said:
the issues are expected, its a port. by nature, ports will be buggy and have issues. but who knows, maybe they will eventually fix them, or not, the next android version will probably be out long before everything works on the port.
Click to expand...
Click to collapse
Not a port
simms22 said:
the ports not a port? lmao
Click to expand...
Click to collapse
Lmao nope
TheLastSidekick said:
Lmao nope
Click to expand...
Click to collapse
People don't seem to understand that it's CM11 Snapshots lol.
I been using it for couple days now. Lots of great features and it runs very smooth! I am coming from Android L; first i tried PA beta which I thought was very laggy with issues. Then i tried cm11 ROM. I did noticed the battery drainage but its not too bad.
simms22 said:
the ports not a port? lmao
Click to expand...
Click to collapse
Thought CM11s also was based on M8 but no...
After some reading I've realised how awesome is the real CM11S, lots of fearures are missing here
It gives me a weird feeling... "You'll never get the OPO ROM mwahaha" :/
Port as a reference to the thread's name
The OP call it CM11S Port for Nexus 5 so I did
1.5 feedback
badboy47 said:
I been using it for couple days now. Lots of great features and it runs very smooth! I am coming from Android L; first i tried PA beta which I thought was very laggy with issues. Then i tried cm11 ROM. I did noticed the battery drainage but its not too bad.
Click to expand...
Click to collapse
1.4 build was smooth but has some anoying bugs.
So went to Purity+ after L Preview and now I'm using v1.5 , QuickBoot and Bluetooth problems seems to be solved, battery drain is maybe a hardware issue.
Hello everyone,
i have currently the issue that my device sometimes doesn't recognize a second/third touch input. This happens for example in some racing games like Trials Frontier or GTA 3. While i press the gas pedal other inputs are sometimes not recognized which leads to an unplayable game.
I currently use smiui 5.11.19 and i am not sure if that's the reason. Same problem with the developer rom.
Does anyone else face the same problem and knows an answer?
I see that issue on the dev roms and on the mokee rom too. Never tested the stable chinese rom, so I don't know if there are any differences regarding the drivers/kernel between that version and all others.
But yeah, simply typing on this device can become infurating because of the touch/multitouch issues.
FrankBullitt said:
I see that issue on the dev roms and on the mokee rom too. Never tested the stable chinese rom, so I don't know if there are any differences regarding the drivers/kernel between that version and all others.
But yeah, simply typing on this device can become infurating because of the touch/multitouch issues.
Click to expand...
Click to collapse
I've tried Cyanogenmod and the problem also occured there. Something is not working correctly on the software site.
I used the touchscreen test which can be found by pressing multiple times on kernel version in about phone. With one finger on the screen everything works fine and the border is correctly recognized by the phone. With multitouch you can see that a small area at every border is not reachable. Maybe i try if the problem occurs in the stable rom. Very weird... :silly:
Yes, I also have this problem along the sides of screen. It's unplayable in games, here the video https://www.youtube.com/watch?v=uPC7Z2ploxc
instadroid said:
Yes, I also have this problem along the sides of screen. It's unplayable in games, here the video
Click to expand...
Click to collapse
The weird thing is that a buddy of me has huawei where i could produce the same problem with multitouch in the test(can't reach the border of the screen by touch) but gaming and all multitouch gestures work flawless. It would be nice if this could be patched somehow...
I dont have this Problem
How many times are you going to post this topic? Maybe something is wrong with your digitizer. Mine works fine.
I have the same pb. Probably hardware related if not everybody has it. I think I recall the Mi4c is sold with 3 different versions of the screen, so it could be they use different hardware for touch recognition as well. Let's hope there is a software fix, but I am not very confident over this...
Had this problemen too, untill I updated to the newest version from Xiaomi.eu and disabled edge-tap! (Didn't use it anyways)!
Worth trying!
Bakpoeder said:
Had this problemen too, untill I updated to the newest version from Xiaomi.eu and disabled edge-tap! (Didn't use it anyways)!
Worth trying!
Click to expand...
Click to collapse
eu rom has miui camera app?i am not getting good battery time on cm12
Bakpoeder said:
Had this problemen too, untill I updated to the newest version from Xiaomi.eu and disabled edge-tap! (Didn't use it anyways)!
Worth trying!
Click to expand...
Click to collapse
I am on CM12.1, and couldn't find an option to disable edge-tap. Although I can see it is active.
Anyone knows if there is a way to disable it?
I believe the CM13 version of Subliminal also has working edge-Tap...
Anyone on CM had luck with disabling it? (if that's an option)
Options -> ROM extra settings
Sent from my Mi-4c using Tapatalk
The-Albatross said:
Options -> ROM extra settings
Sent from my Mi-4c using Tapatalk
Click to expand...
Click to collapse
Thanks, I'll install CM13 and give it a try... This multi-touch is really annyoing in arcade games
Bakpoeder said:
Had this problemen too, untill I updated to the newest version from Xiaomi.eu and disabled edge-tap! (Didn't use it anyways)!
Worth trying!
Click to expand...
Click to collapse
Didn't work for me, still experiencing the issue... ?
Enviado desde mi Mi-4c mediante Tapatalk
Just letting everybody know that their has been a Tesla ROM developed for Clark. Their is a test version only right now but its still bad ass! Go to android file host and search it. I'm sure we will see it posted to XDA sooner then later.
Great news!
I really liked their rom and used it on my Samsung Galaxy S2.
It was awesome!
But I'm already used to moto display, chop chop for flashlight And double twist for camera...
Will be hard to switch to AOSP for me ?
inb4 thread closed
newHere:) said:
Great news!
I really liked their rom and used it on my Samsung Galaxy S2.
It was awesome!
But I'm already used to moto display, chop chop for flashlight And double twist for camera...
Will be hard to switch to AOSP for me
Click to expand...
Click to collapse
Chop chop and double twist are working on it. I've been running it for the last few days now, and it's my favorite ROM. The 03/12 build is better than the 03/13 build. The 03/13 build was chewing up my battery.
spotmark said:
Chop chop and double twist are working on it. I've been running it for the last few days now, and it's my favorite ROM. The 03/12 build is better than the 03/13 build. The 03/13 build was chewing up my battery.
Click to expand...
Click to collapse
Is there a save to SD option on camera? I know the AOSP camera doesn't have this option but some of them include CM camera
Makalicious said:
Is there a save to SD option on camera? I know the AOSP camera doesn't have this option but some of them include CM camera
Click to expand...
Click to collapse
Nope, you have to move them manually.
I tried it for a day and it seemed very unstable and buggy. But so was Broken OS, and PureNexus. I don't know if it's my phone, or just the ROMs becoming more unstable than they were in February. I haven't found a DD yet.
HikingMoose said:
I tried it for a day and it seemed very unstable and buggy. But so was Broken OS, and PureNexus. I don't know if it's my phone, or just the ROMs becoming more unstable than they were in February. I haven't found a DD yet.
Click to expand...
Click to collapse
Surprised to hear that. Mine is running like a champ. Best ROM I've used so far, imo.
spotmark said:
Surprised to hear that. Mine is running like a champ. Best ROM I've used so far, imo.
Click to expand...
Click to collapse
Yeah :/ I had really high hopes. At times it seemed great. I wished there was a way to turn their theme from holo blue to red! I've been using black and red themes lately. I wish I could remember the specific issues I had with this one. I know Broken would be working fine, then just crash, and not power up again. Pure nexus only had 3/4 of the features working, and had all the notofication and scrolling lag that the CM ROMs have. Who knows. Could be my device.
HikingMoose said:
Yeah :/ I had really high hopes. At times it seemed great. I wished there was a way to turn their theme from holo blue to red! I've been using black and red themes lately. I wish I could remember the specific issues I had with this one. I know Broken would be working fine, then just crash, and not power up again. Pure nexus only had 3/4 of the features working, and had all the notofication and scrolling lag that the CM ROMs have. Who knows. Could be my device.
Click to expand...
Click to collapse
I'm leaning toward it being your phone. Broken ran great for me as did Pure, with the exception of the music bug.
Alpha release is up on their G+ page.
HikingMoose said:
I tried it for a day and it seemed very unstable and buggy. But so was Broken OS, and PureNexus. I don't know if it's my phone, or just the ROMs becoming more unstable than they were in February. I haven't found a DD yet.
Click to expand...
Click to collapse
Do you mind describing how it was unstable and buggy? I need feedback in order to fix issues. It's running very well for me right now. And I'm working on porting EAS from bullhead as well
gmillz said:
Do you mind describing how it was unstable and buggy? I need feedback in order to fix issues. It's running very well for me right now. And I'm working on porting EAS from bullhead as well
Click to expand...
Click to collapse
I apologize, but I can't honestly remember now. I can't remember if that was the one that would have apps close on me, or open on me without any input, or why I used the word unstable and buggy. If I say something is unstable and buggy, it typically means I had significant issues, beyond the normal one or two things that just don't work. But I unfortunately cannot remember.
I would like to note however, I noticed that restoring my apps and data with TiBu seemed to be causing some of my issues with the ROMs from that timeframe. Because I flashed the same purenexus build twice, once with restoring apps and data, and once by reinstalling everything from the play store, and noticed a huge difference. Using TiBu was much buggier, on the very same build. So it might have been that.
Link??
Restoring system data with TB can cause all sorts of weird issues. I strictly use it to restore apps/data for everything else, but not system data.
Sometimes it helps to wipe internal storage too when moving from one rom type to another (ie, stock based to aosp).
I haven't tried tesla rom yet, but may give it a shot in the future.
gmillz said:
Do you mind describing how it was unstable and buggy? I need feedback in order to fix issues. It's running very well for me right now. And I'm working on porting EAS from bullhead as well
Click to expand...
Click to collapse
Thank you for all of you rom maker, you make clark more wonderful . The only hope is to the aosp based rom can support dual sim, by now only brokenrom support dualsim as I know. I tried DU , orion, purenexus and your tesla, they all not support dualsim .I m glad to help to the best of my ability like make logcat ,etc.
humor2008 said:
Thank you for all of you rom maker, you make clark more wonderful . The only hope is to the aosp based rom can support dual sim, by now only brokenrom support dualsim as I know. I tried DU , orion, purenexus and your tesla, they all not support dualsim .I m glad to help to the best of my ability like make logcat ,etc.
Click to expand...
Click to collapse
If you could get a logcat on boot and send output of adb shell getprop
gmillz said:
If you could get a logcat on boot and send output of adb shell getprop
Click to expand...
Click to collapse
Ok, I will do it right now .
View attachment 3692858
View attachment prop.txt
Here comes the logcat and prop !
THis is for the Tesla0312 rom
============================
and this is from BROKEN ROM:
View attachment broken.txt
View attachment prop-broken.txt
Anyone else having the 2 below issues or do I need to clean flash again...
1. Holding recents for last app will flip to last app then open recents (not just flip to last app). I tested this over and over with same result.
2. Google maps works but I can't see streets. The GPS showed I was home but nothing else
As the title says, this is one of the best v6 Google Camera app I've found. I don't remember the source but am pretty sure it's from bulkin043.
File is in my Drive here
i am facing charging issue when notification light is on the device is charging and when the light is off the device is not charge but show the symbol of charging in pixel experience rom.
mohit.D298 said:
i am facing charging issue when notification light is on the device is charging and when the light is off the device is not charge but show the symbol of charging in pixel experience rom.
Click to expand...
Click to collapse
Wrong thread mate
from 4pda?
ovistranger said:
from 4pda?
Click to expand...
Click to collapse
Yes, you are right. It's from bulkin043 from 4pda.
No force close issue with this build?
Axl_Mas said:
No force close issue with this build?
Click to expand...
Click to collapse
No FC so far
Doesnt work.
crash at start.
Samsung sensor, 8.1 Oreo.
Sony98 said:
Doesnt work.
crash at start.
Samsung sensor, 8.1 Oreo.
Click to expand...
Click to collapse
Check Camera2API. I haven't tried it on Oreo.
crzo said:
As the title says, this is one of the best v6 Google Camera app I've found. I don't remember the source but am pretty sure it's from bulkin043.
File is in my Drive here
Click to expand...
Click to collapse
thx for this...tried now several versions of gcam 6.*....none of them really worked well.... this one is the most stable for me so far, though i still have crashes ever and anon (after taking picture, but seldom now) . not as stable as gcam5 (which is the last version works perfect 4 me) but definitely best working v6 version for me.
I'm on RR 7.0.2 with samsung sensor.
which settings do u use? default?
-=Joker=- said:
I'm on RR 7.0.2 with samsung sensor.
Click to expand...
Click to collapse
I'm using PE by Aryan Kedare with same sensor.
which settings do u use? default?
Click to expand...
Click to collapse
Didn't do any changes except turn off Slo-Mo in Advanced settings because it fails to work.
crzo said:
I'm using PE by Aryan Kedare with same sensor.
Didn't do any changes except turn off Slo-Mo in Advanced settings because it fails to work.
Click to expand...
Click to collapse
ok, thx! maybe i'll switch to PE since i wanted to try anyway...would it go along with better gcam performance even better
Can confirm.
Thus is the only 6.x version with nightsight and focus trackng that doesnt crash.
Can someone implement the sunfix on newer 6.2.30 gcam?
D'ont crash gere, but a lot of noise in front cam, this mod d'ont have how to change the Base of front cam. How to fix It?
I am using GCam 6.2.030 RN7 build by BSG on Pixel Experience CAF android 9 Pie with samsung sensor. This gcam version works fine as well on my device.
Robadel said:
D'ont crash gere, but a lot of noise in front cam, this mod d'ont have how to change the Base of front cam. How to fix It?
Click to expand...
Click to collapse
Solved, using the last Bulkin Gcam (6.2.030) , I just started using Franco Kernel and no crash or FC.
Any ideas why crash on launch? I'm on Syberia OS Pie with OV sensor
I'm using aosp extended based on Pie and currently I'm using Sulphur gcam from insanity but is there any better one for me?! and does flashing a custom kernel make any difference cuz I'm using the stock one with aosp..
Pls help, im on havoc os poe for mido and except some gcam apps most of them says app not installed for me while installing, i don't know much about these gcam things like Samsung sensors or whatever but if someone helps I appreciate, thanks
Is there any Android 12 rom that has the FOD and dttw working property with the always on display? Thank tou.
radaan said:
Is there any Android 12 rom that has the FOD and dttw working property with the always on display? Thank tou.
Click to expand...
Click to collapse
Hey there,
So far I tried derp, pixelex., Nameless and Cr droid without any luck.it seems that the aod is kind of broken on all of them, it works sometimes and sometimes not, I could not figure it out.
Also they are all bit stable enough for me, to much hickups, but that is just my opinion.
Greetings
TanakaX5 said:
Hey there,
So far I tried derp, pixelex., Nameless and Cr droid without any luck.it seems that the aod is kind of broken on all of them, it works sometimes and sometimes not, I could not figure it out.
Also they are all bit stable enough for me, to much hickups, but that is just my opinion.
Greetings
Click to expand...
Click to collapse
Thanks for the reply. Finally someone. I tested a few too and there is not one that has dt2w on the aod working. The rest works Just fine, at least considering my daily use.