yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] andre0005:
Flash the provided zip from the op.
[ONE Original Android Development] smint86:
Usually I just ignore posts like yours. But in your special case I'd suggest you get a lawyer and sue sultanxda for compensation. It's really not acceptable, forcing you to install a ROM with features you don't want. Unbelievable...

Swyped via Tapatalk
[ONE Original Android Development] Adikovec:
but its cool xD
[ONE Original Android Development] andrew2511:
Dear [MENTION=4800121]Sultanxda[/MENTION] I can say that finally the glitches with Sharp screen are gone! Thank you so much :D

Meanwhile somewhere on the mountains of South Italy: After a long deep sleep, here they come back...
[ONE Original Android Development] chronaden:
Does this new build fix the issues with triggers? Fx when I join my home WiFi, my normal profile is activated, disable lockscreen and normal ring tone. This kinda breaks the phone on current build, and I have to force shutdown by holding power button. This wasn't an issue a few builds back.
[ONE Original Android Development] madsponge26:
Oh my.... Did you read whole OP? This answer is there. Btw i ignore this message.:p
[ONE Original Android Development] rondog2:
Here is the Hydrogenos firmware.

https://www.androidfilehost.com/?fid=24052804347825945
[ONE Original Android Development] hellcat50:
Just ignore my post. I have a bad day today after the incompetent OnePlus support yesterday. So sorry for my post.

btw i flashed the underclock removal ZIP and for me it's still underclocked (I wiped data and then flashed the newest version oft the rom+underclock removal+ AK kernel. That worked well with the 10.11 . version.)
[ONE Original Android Development] krones:
I am sorry , but you mean ' modem ?

Στάλθηκε από το A0001 μου χρησιμοποιώντας Tapatalk
[ONE Original Android Development] renaltosonylevi:
Make sure your CPU is below 42° before complaining. Anything above that temp and your phone will be under clocked.

That zip is only useful if you regularly live most of your life below 20°.

Car analogy time, there is a slow car in front of you do you drive at full speed then slam on the brakes or ease up beforehand and drive up behind the the slow car smoothly.
[ONE Original Android Development] hellcat50:
Dude you are right, thanks. :victory:
[ONE Original Android Development] rondog2:
yes
[ONE Original Android Development] krasny2k5:
[MENTION=4800121]Sultanxda[/MENTION] just flashed (clean) 20151017 here and still getting graphics corruption when i wake up from sleep. Sharp panel here.

Thanks for your work
[ONE Original Android Development] TonySuperPony:
I also have a sharp panel. But I don't know what glitches everyone is talking about. Could you tell what the problem is you get with sharp panel?

Verstuurd vanaf mijn A0001 met Tapatalk
[ONE Original Android Development] zBear:
in the latest build I get a good speech quality

not great, like with fluence enabled (10.04 rom), but acceptable

so, if anyone, like me, was stuck with fluence, I recommend you to try the latest rom, you may like it
[ONE Original Android Development] areyie9292:
sorry for asking about modem. i have flash the latest modem hydrogen os modem, but, proximity sensor not working. is it have another step to flash it? i think hydrogen os modem more better, and give me good signal.
[ONE Original Android Development] Sp4rsh:
wont charge with power bank

i recently got a power bank and it wont charge the phone when its locked, it works fine when the phone is awake though, it worked on normal cm 12.1 so i'm guessing its a kernel bug, any help would be appreciated.
[ONE Original Android Development] Redicus:
Anyone knows how to cancel cm update? I started 4 ota updates by mistake and i cant stop them. There is no option to stop, only to download the 5th time.
[ONE Original Android Development] andrew2511:
When you wake up the phone from deep sleep you will see a weird an 1/4 of second "CRT effect" glitch
[ONE Original Android Development] Ribery771:
How can I check what panel i got?
[ONE Original Android Development] 69gm:
Sorry OT but you might want to get the newer banner. Yours is getting cut off...
[ONE Original Android Development] gd6noob:
LMAO.. damn it... i knew i should have waited 1 more day... I was on the build before Oct 11 and hold out until the 16th... lol...

Good Job Sultanxda... cant wait to reflash
[ONE Original Android Development] ~KV:
How's the idle drain on the latest version? I've noticed high idle drain, although SOT is good...
[ONE Original Android Development] martikung:
Can i actually encrypt my device? Rooted and twrp installed.
[ONE Original Android Development] meiax93:
Do you clean install before flash this ROM? :eek:

Mine OPO have no problem charge phone with power bank ;)
[ONE Original Android Development] sToRm1nG:
Yes, but you have to flash TWRP 2.8.6.1 as encryption is broken again in 2.8.7.0. It has to be 2.8.6.1 as this TWRP supports hardware encryption.

https://dl.twrp.me/bacon/
[ONE Original Android Development] martikung:
Alright, any future updates can be installed like usual, Yes?

Thanks ?
[ONE Original Android Development] aurocha:
Hi,

Out of mere curiosity, tried to find out the manufacturerer of my phones screen.

So, I switched the phone of and back on, and, with Terminal, piped the output of dmesg to a text file and then read it.

It's a JDI.

But found out a couple of things that alarmed me:

Q1: Is my GPT corrupted? Any way I can recover it?

Q2: Are you guys also getting orphan inodes in your /data partition?

Regards,

- aurocha
[ONE Original Android Development] Limewirelord:
I already gave it root access, it reboots with no problems when I do soft reboot.
[ONE Original Android Development] NeeDXxPT:
[MENTION=4800121]Sultanxda[/MENTION] you will do this to your rom?

http://www.xda-developers.com/chromium-optimized-for-snapdragon-devices/

Enviado do meu A0001 através de Tapatalk
[ONE Original Android Development] CaptainZap:
[MENTION=4800121]Sultanxda[/MENTION] I think this would be a great addition for your next update !
[ONE Original Android Development] sdmark:
Hey [MENTION=4800121]Sultanxda[/MENTION], just wanted to say thanks for this rom. I have been going back and forth between my opo with your rom and my op2 with oxygen os (having some LTE issues with the op2)...every time I come back to this and the opo I'm amazed how much faster and smoother it performs over the 2. Keep up the good work.
[ONE Original Android Development] 1ceb0x:
The only thing i can think of is Selinux to Permissive. I have it, though I do not recommend it in the sense that, you do what you think it's right for you :)
[ONE Original Android Development] Miikli:
Yes, it looks promising. Firstly the Snapdragon camera and now the Chromium browser. I'm happy I don't have an exynos processor ?.
[ONE Original Android Development] coen22:
Looks great!

But I do have a question. I have a beats headset of which the volume buttons work on my iPad, but not on Android. Is it possible to get them to work via the kernel, by changing the threshold values (in mA)?
[ONE Original Android Development] 1ceb0x:
They need to be compatible with Android as i don't think you can resolve this from the kernel.
[ONE Original Android Development] Zalbu:
Xposed broke for me earlier too, installing the newest SuperSU, Xposed Framework and Xposed Installer fixed it. More specifically, going from the alpha1 to the alpha4 installer fixed it.
[ONE Original Android Development] bounti:
I don't know why, but ever since the 11th build, my phone keeps bootlooping when I flash this rom. I keep having to revert to the 4th build to get back into the os. Is something new required that I'm not aware of? New firmware perhaps? I use OnePlus Firmware 6-17-15. I also use AK kernel, tk gapps and xposed. Even just flashing the firmware and rom alone, I have the same problem. Any suggestions?
[ONE Original Android Development] floxigen:
Maybe a problem with ak kernel

Sent from my Oneplus One MasterRace
[ONE Original Android Development] johnb380:
Make sure your wiping system because that's where Xposed add-on.d is saved. If your wiping system data cache and dalvik when clean flashing and only flashing Rom and gapps then idk.
[ONE Original Android Development] bounti:
Thx for the response. But I'm beginning to think the problem is with xposed.

I don't fully understand. Are you saying I should wipe system, cache and dalvik cache? I usually only wipe cache and dalvik. Won't I have to re-install my apps after wiping system?
[ONE Original Android Development] johnb380:
No if you are dirty flashing wipe system cache and dalvik and everything will be fine except you won't get a bootloop from Xposed!
[ONE Original Android Development] bounti:
That's exactly what I usually do. Wipe cache and dalvik then flahs what's needed. But apparently Xposed doesn't work anymore with the latest version of this rom. Does it work with anyone else?
[ONE Original Android Development] johnb380:
No wipe system then cache then dalvik cache. How are you missing me saying to wipe system. I'm saying to wipe SYSTEM TOO.
[ONE Original Android Development] bounti:
Well that's what commas were made for lol. "System cache" and "system, cache" are 2 different things.

At any rate, I'll give it a try.
[ONE Original Android Development] johnb380:
Ya my bad I'm watching the Buckeyes vs Penn State football game so I'm pre occupied right now!
[ONE Original Android Development] ksigit:
This is the checklist, make sure you have them:

# xposed installer version 3.0 alpha4

# xposed-v75-sdk22-arm.zip

# xposed-uninstaller-20150831-arm.zip

I dirty-flashed numerous times, and the only occasion it stuck at bootloop, is when upgrading to 20151001 build. Apparently latest v75 is required, while I was still on v74 version. Uninstall xposed using the uninstaller zip and reflashed v75 solved the problem.

Hope this helps.
[ONE Original Android Development] bounti:
Ahhhh. Thx ksigit. I was on v74 and didn't realise v75 had been released. Just flashed it and my phone boots as it should! :D
[ONE Original Android Development] ikjadoon:
You have to force close and clear the cache of the "Download Manager". It's a little crazy, but I'm too lazy to make a feature request to CyanogenMod.

I've had this issue, too, and I came from a clean build.
[ONE Original Android Development] AbhishekS:
On the latest build. There is a lag while the phone returns to the home screen after clearing all apps.

Am I the only one?
[ONE Original Android Development] imam.krismanto:
Waiting [MENTION=4800121]Sultanxda[/MENTION] compile Android 6 AOSP source, amazing...!!
[ONE Original Android Development] FirstBurst:
Seems to be working fine for me so far. No lag. Try reflashing?
[ONE Original Android Development] sneakerspark:
+1. Depends on the number of apps opened.
[ONE Original Android Development] renaltosonylevi:
Don't hold your breath.
[ONE Original Android Development] crazix:
Theme Chooser depends on theme developers and way they theme certain elements. Been using TRDS for quite sometime hence seeking any possibility. :)
[ONE Original Android Development] nsmart:
Can you explain what is broken with twrp 2.8.7.0 and hardware encryption? I am using twrp 2.8.7.0 and hardware encryption and have not noticed any difference to version 2.8.6.1.
[ONE Original Android Development] imam.krismanto:
Baseband unknown, No simcard after flash newest modem, why?
[ONE Original Android Development] AcmE85:
Because wrong TWRP Version

Please read!!!!!!
[ONE Original Android Development] Arju:
What is your twrp version? Have you tried flashing the version before? Is your baseband and sim card recognized when flashing an older version?
[ONE Original Android Development] InsightGoalie:
Since a lot of people recommended this ROM I flashed it to try it out. I'm having a few issues though. Firstly, I'm coming from CM12.1 nightlies. I wiped, installed this ROM, installed gapps, then set things up like normal. Everything seemed okay at first, but at some point my power button became less than responsive when waking the device up. It would take anywhere between 1 and 13 presses to get the screen to wake. I've wiped, reflashed, and created a nandroid backup that doesn't seem to suffer from the same problem. The problem seems to come back if I install Xposed v75. Another issue I'm having is that the screen shuts off in a call, it won't even come back on if I press the power button. If you call something with a phone tree it is utterly useless. Lastly, if I try to dirty flash the 17 Oct build over it, it boot loops. Has anyone seen any of these problems or have any suggestions?

Edit: I take back what I said about it seeming related to xposed. It started doing the unresponsive power button thing again, this time without me changing anything. Very confused.
[ONE Original Android Development] imam.krismanto:
Thank you, i flash with 2.8.6.1 version. Success with 2.8.7.1 version
[ONE Original Android Development] Arju:
Flash 2.8.6.0. That version should not give you any trouble.
[ONE Original Android Development] sToRm1nG:
Yes this should be possible. Anyway, it is always better to have a backup before trying new stuff. :)

There were people reporting issues with unlocking the encrypted partitions when entering TWRP. I just know that this should not be an issue with 2.8.6.1. :)

*EDIT*

Here are the corresponding GitHub issues:

2.8.4.1-2.8.6.0: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/333 (Fixed in 2.8.6.1, there is also a link to an unofficial release by Dees-Troy inside the issue)

2.8.7.0: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/454 (Dees-Troy pretty much said he has no time looking into it and therefore I guess you are better of with 2.8.6.1)
[ONE Original Android Development] Limewirelord:
Yeah, I honestly don't know what's wrong. I've got the lastest SuperSU, Xposed Framework, and Xposed Installer. It just refuses to work. I'll probably factory reset sooner or later and mess with it in a release or two.
[ONE Original Android Development] jvybihal:
Yup, this would be lovely if added to next build.
[ONE Original Android Development] BarnOwl:
Just download it here, great new browser! ;)
[ONE Original Android Development] Solid-Dado:
Hi, I'm trying to update from a previous version of this Rom but when I dirty flash the newest build my phone get stuck in bootloop, I use root and xposed.

Did I do something wrong?

Thanks
[ONE Original Android Development] Tymp:
Hi guys, this is the problem I get with wifi transfer (to my nas or via wifi direct) since October 11 build:

https://youtu.be/P-ARobvj56M

I also have the same problem with cm12.1. Does it depend on the wifi driver? Is there a way to fix it without rolling back to previous builds?
[ONE Original Android Development] ksigit:
Flash latest xposed v75..
[ONE Original Android Development] cbendan:
[MENTION=4800121]Sultanxda[/MENTION]

Gestural writing doesn't work in lastest 17th build. Clean flashed and Pico Open Gapps.

Edit: I've reinstalled gapps and still not working. Only with Android keyboard. I've installed swiftkey and gestural writing works.

Edit 2: I confirm it's an Open Gapps problem in the last version.

I've installed Tk Gapps and everything is OK.
[ONE Original Android Development] xermit:
[MENTION=4800121]Sultanxda[/MENTION] mobile data not connecting after wifi is lost :( i'm on latest build with 241 firmware. Came from 1004 build with hydrogen firmware, where i didn't had this problem.
[ONE Original Android Development] floxigen:
Same here rolling back to 1004 like last week

Sent from my Oneplus One MasterRace
[ONE Original Android Development] sneakerspark:
Battery life entirely depends on one's use. Maybe you play plenty of hardware intensive games. Whats ur avg SOT?
[ONE Original Android Development] mattardz:
I typically don't play any games on my phone. Just periodic social media checking and web browsing. I'm lucky if I get 4 hours of SOT, normally i get closer to 3 -3.5.

I have generally poor cell reception where I'm at, especially in my office, so I don't expect to get as good battery as some others. That can't be the only issue though.
[ONE Original Android Development] ogrillion:
Are you on mobile data connection the whole time? Most posting good SoT are on WiFi the whole time.

I generally am always on WiFi but when I am not my battery drains pretty quick
[ONE Original Android Development] renaltosonylevi:
Generally I think comparing different peoples screen on times is meaningless because as stated above different environments and use will have a vast affect on battery life.

Me personally I spend a lot of time in weak signal area's and I do a lot of traveling. If I spend the day at home constantly on WiFi my screen on time almost triple. Worst case about 2 hours sot .

Finally apart from wanting a phone that will comfortably last the day I am not particularly interested in battery life. My focus has always been on performance first.
[ONE Original Android Development] ImmortAlex:
Don't forget, that we have three different screen panels: JDI, Truly and Sharp.

AFAIK, Sharp has more power consumption than JDI (but is better in term of quality).
[ONE Original Android Development] dwaipayanray95:
how do we check which panel do we have and how to change? and won't the drivers be different for every panel? then how? anyway how can I check?
[ONE Original Android Development] sneakerspark:
Changing panel means changing the whole damn screen. You r better off with what u have currently.
[ONE Original Android Development] DerRomtester:
[MENTION=4800121]Sultanxda[/MENTION] do you think this problem here https://jira.cyanogenmod.org/browse/BACON-1309 is realted to the camera drivers or the camera libs or hal or sth else ? This does not happen on your rom, only on cm based roms. If it is a problem with the driver i think i could merge the original drivers into the cm drivers to solve the problem. But i want to be sure that this is related to the driver in the kernel. I don't want to start that project without knowing if it has any success.
[ONE Original Android Development] ImmortAlex:
The display type can be found by typing these commands in terminal emulator just after reboot (you need to be rooted):

su

dmesg | grep -i panel

Mine shows "Panel name = jdi 1080p"

Yes, they are different.

Just look at the beginning of this topic: Sultan thougth that only JDI panels is actually used in production units and removed all other drivers. And than quickly user appeared who have Sharp one.
[ONE Original Android Development] Deepak Vishnu:
All the indian opos are jdi ...
[ONE Original Android Development] dwaipayanray95:
[MENTION=4800121]Sultanxda[/MENTION] also I faced an issue the camera focuses a bit too quickly but when in HDR it just wouldn't focus at all...I'll have to restart the camera app or keep switching modes till the time it starts working....also please look into the 120fps thing

---------- Post added at 12:47 PM ---------- Previous post was at 12:46 PM ----------

[/COLOR [MENTION=4800121]Sultanxda[/MENTION] also I faced an issue the camera focuses a bit too quickly but when in HDR it just wouldn't focus at all...I'll have to restart the camera app or keep switching modes till the time it starts working....also please look into the 120fps thing
[ONE Original Android Development] Sultanxda:
HAL. Camera drivers in the kernel control the actual camera hardware (ex: sending commands to the actuator hardware to make it move), whereas the HAL and userspace in general control higher-level camera functions, such as image processing and HDR. Playing with the camera drivers in the kernel will probably fix none of the issues with the CM camera.

I'm not a camera engineer; I have absolutely no idea how to implement 120 FPS stuff :silly: Also, I can't control how often continuous autofocus decides to fire.

Focus isn't working with HDR mode on the Google Camera app after the new Google Camera update, but it works fine with the default camera app included in the ROM. I won't try and fix this issue as Google Camera is closed source (just looked at the log messages for it and I have no idea what's going on).
[ONE Original Android Development] markvd90:
Quoting this because I'm wondering the same.

Smartmax has been quite awesome on other kernels so far.
[ONE Original Android Development] Sultanxda:
Tested it for the last 15 minutes; I'll add it in the next build and set it as the default to see how it goes. From the outside, it seems to behave pretty well, but the code is very messy and convoluted (and I'm way too lazy to clean it up). If I get good results with it then I'll keep it as the default and turn a blind eye towards the messy code :P

[MENTION=713062]Bugenhagen[/MENTION] I decided to forcefully disable the vibrator while videos are recording, since you seem to have made a good point (the vibrator on this thing is probably louder than my ringtone).

https://github.com/sultanxda/androi...mmit/276c30b007be0bd2bca63512fb8571e530079440

https://github.com/sultanxda/androi...mmit/d3b3856886ca986da8377df54c59afcf8376a122
[ONE Original Android Development] Bugenhagen:
Cool, thanks! Will you add this to the next version, or should I try to make this code work myself? (I'm just a simple user, have no idea how these things work)
[ONE Original Android Development] markvd90:
[IMG="hb"]http://i1.kym-cdn.com/photos/images/newsfeed/000/641/298/448.jpg[/IMG]

Sorry, can't wait to test it:p
[ONE Original Android Development] tiny4579:
Thoughts on CM's decision to go with this branch for CAF?

https://github.com/CyanogenMod/andr...mmit/f972e573feb34c9979cb2c0606c22135ba0ddfbf

Would it improve anything you think since it's supposedly the right branch for 8974 chipsets?

Also, have you seen this and do you think it will be any benefit?

http://xdaforums.com/android/software-hacking/adreno-idler-idling-algorithm-devfreq-t3134872

I've noticed you've already tweaked the GPU governor as it is since the idle clock is 27mhz.

According to this, it seems to be using 330Mhz a lot more frequently than 200MHz.

cd /sys/devices/*kgsl*/devfreq/*/
while true; do cat trans_stat; busybox sleep 0.1; done
[ONE Original Android Development] joefso:
Any interest in integrating find 7 camera hall?
[ONE Original Android Development] Sultanxda:
Next version.

CAF branch doesn't matter so long as kernel-space is compatible with userspace. The current CAF branch (LA.BF.1.1.1_rb1.25) is very close to that special 8x74 tagged release; it's close enough that it shouldn't cause any firmware incompatibilities, so I'm pretty sure using the latest LA.BF.1.1.1_rb1.xx release is fine.

330MHz is used for the UI (200MHz isn't fast enough to guarantee no UI lag from the GPU). I read over that thread and tried reproducing the issue it described, and I couldn't reproduce it (GPU went down to 200MHz while watching YouTube). I also looked at some of the code, and I saw a few weird things that weren't explained (ex: randomly removed an SCM call to TZ in some PM stuff for devfreq).

As for the 27MHz thing, that's the GPU's slumber freq (I never tweaked the GPU). 27MHz isn't usually seen anywhere in sysfs, but myfluxi exposed it in KGSL's sysfs node: https://github.com/sultanxda/androi...mmit/8517694316cdb45e1a258d59030e406a0be80611

while true; do cat /sys/devices/fdb00000.qcom,kgsl-3d0/kgsl/kgsl-3d0/gpuclk; busybox sleep 0.1; done

The GPU enters slumber mode whenever the screen is static.

Find7 camera HAL is a slightly smaller version of the CM camera HAL. I tested it and it has some of the same bugs (such as artifacts in camcorder).
[ONE Original Android Development] Raul027:
Quick bug notice: when dismissing alarms from the notification area they seem to come back after like 30 minutes. So alarms are not really able to be dismissed.
[ONE Original Android Development] raul.lopez1958:
[MENTION=4800121]Sultanxda[/MENTION]

is it possible in the future to add a gradient effect on the lock screen, as it gets in the Lockscreen wallpaper Xposed module for KitKat?

It will be great.

Cheers