yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] sbw17:
First - the ROM is very very fast!!

Few issues I experienced ( copying form 1+1 official forum)

The exit point

// My OPO was purchased in Austria 2 years ago. First year all was good, then ppl started to complain that phone is not reachable sometimes.

I noticed that no reception and no data services were for few minutes after boom ! it's coming back again. Phone located on same place - on the table.

Sine we have another OPO at home and it's working pretty good on LTE ( Band 3, 1800), I flashed same OS and same baseband, but on second phone the kernel kernel and increment is higher ( OOB settings)

Still the phone is going to H+ in best.

There are few issues i see here:

1. SIM card and APN settings, I'm usinbg virtual provider services and once I switch to it's "mother" 3G APN settings I get pretty stable H+ signal and sometimes LTE.

Cross-Cross SIM. Mine SIM works bad in second phone. the second phone SIM gives H+ on mine

So, first of all the SIM will be replaced.

Again, I wanted to get LTE services on second DIM in my phone, but it doesn't. This phone will go to kid kid in a week, I'm trying to get stable services ( data/voice) on it.

So:

I have now: Kitkat 4.4.4

cm-11.0-XNPH33R-bacon-signed-fastboot - flashed by fastboot

Unlocked bootloader

Rooted + TWRP recovery

Baseband : MPSS.DI.2.0.1.c7-00020-M8974AAAAANPZM-1//

The stuff were done.

Flashed Sultan ROM using TWRP exactly as described in Installation Instructions.

NOT ! flashed Frankenshtein modem

Currently I have the following:

First of all I switched to another carrier, which coverage is much better in my area

I finally burned CM 12.1 Sultan ROM.

Currently running on the following:

CM version: 12.1-YOG7D-20160410-Stable-Sultan-bacon

Android version: 5.1.1

Baseband: DI.3.0.c6-00241 ( the one from ROM)

I have H+ pretty stable signal at work place ( not tested at home yet). no LTE although.

Tried to switch to AUS band in 4636 menu and still no LTE

Once I try to check the avialable network ( Settings - Mobile networks), I have no output networks in this menu, although calls are working fine.

Is it a way I still can get a LTE on phone? Somebody recommended MM official ROM. I'm really illustrated with this phone...

Thanks

Link to 1+1 thread
[ONE Original Android Development] aryanbang:
That's cool ad hell
[ONE Original Android Development] Matrix1999:
Just installed this today and it is really fast. Thank you!!
[ONE Original Android Development] Wil53664:
[MENTION=4800121]Sultanxda[/MENTION] im stuck at 100% what should i do??

---------- Post added at 10:31 PM ---------- Previous post was at 10:31 PM ----------

[/COLOR [MENTION=4800121]Sultanxda[/MENTION] im stuck at 100% what should i do??
[ONE Original Android Development] kaz93:
Just want to ask, I hope this doesnt came off as rude, but why are you saying that the gamma hacks are dumb and gimmicky. And another thing, I am not sure whether all the cm12.1 rom are like this or not, but I felt that your rom default screen color is very saturated compared to cos12. Is there anyway for me to dial it down to cos12 level ( if there is any changes compared to stock )?
[ONE Original Android Development] Sultanxda:
You can use Savoca's app to control display colors via LCD KCAL (http://xdaforums.com/android/software-hacking/dev-kcal-advanced-color-control-t3032080), or you can use the color calibration tools under LiveDisplay in settings to change display colors.

Why I think CABC is gimmicky/silly: CABC in the CM kernel has 4 use modes (off mode, and 3 other gamma-preset color modes): https://github.com/CyanogenMod/andr...drivers/video/msm/mdss/mdss_livedisplay.c#L60

But 2 of those gamma presets are not used (CABC_IMAGE and CABC_VIDEO modes). Instead, CABC is always set to the CABC_UI gamma preset, and the CABC manager in the ROM doesn't even have code to support all of CABC's modes: https://github.com/CyanogenMod/andr...anogenmod/hardware/AdaptiveBacklight.java#L71

The CABC manager only has two abilities: setting CABC mode to 0 (CABC_OFF) or setting it to 1 (CABC_UI). Therefore, CABC is not actually content-adaptive, it's really just a single gamma preset that gives slightly higher contrast. Even if all of CABC's gamma presets were used, the transitions between a different gamma mode and the backlight's brightness to save power wouldn't be smooth, as CABC's color modes are gamma *presets* (a CABC mode transition would be totally noticeable to the user). Also, CABC doesn't actually touch the backlight's brightness, so it doesn't give any power savings (as the whole idea behind CABC is to increase contrast and reduce backlight brightness to make the screen seem just as bright with the reduced backlight level).

I haven't tried the other gamma hacks (SRE and color enhance), and I'm not really interested in them. Color temperature can already be changed however you want via post-processing in MDSS (examples: LiveDisplay and LCD KCAL), so I see no reason to include the other gamma hacks.
[ONE Original Android Development] imam.krismanto:
Just feed back, WIFI tethering still broken unable to start like previous build..
[ONE Original Android Development] kaz93:
Oh, thanks for the explanation. That explain why the changes are instantaneously visible(not smooth) and a bit annoying to be honest duento videos become washed out during bright lighting. However, since CABC is said to have energy saving benefit, I just let it on. But the contrasty screen is quite irritating too since videos look darker since I'm a fan of pre 30o calibration (therefore I tried to emulate that with rgb adjustment only since that I felt that the gamma level is just fine), i dont know if it saturation or gamma that causes this. I thought it is the work of CABC bit since that you said you did not include it, i might try to reduce it a little using the inbuilt display tool.
[ONE Original Android Development] ghmail2:
can you continueing providing us a omni rom with your kernel sultan? like once a week? really tired about the cm.
[ONE Original Android Development] MobileThrowAwayAcc:
I really hope the WiFi tethering gets fixed soon.
[ONE Original Android Development] Sultanxda:
What? WiFi tethering is working perfectly fine for me... I even uploaded the new build while tethered to my phone (and my phone was running the new build while I was tethered to it).

No. Something was seriously wrong with the RIL in my Omni builds... My Omni build broke my mobile data, and I couldn't get it working no matter how many ROMs I flashed via fastboot (even CM11S wasn't working). Finally, I somehow managed to get my mobile data to sputter back to life with the official CM12.1 nightly, so I'd rather not touch my Omni builds again.
[ONE Original Android Development] 1/4 Life:
Hey [MENTION=4800121]Sultanxda[/MENTION], I just noticed you implemented the kexec hardboot patch in the latest version. I'm not sure if you know, but that completely breaks encryption it's current incarnation.

Did you ever hear back about those encryption changes to fix mounting data in TWRP?

That's all. Glad to see KCAL and the fixed compass!
[ONE Original Android Development] darkobas:
I have a request if you could add more 16:9 camera resolutions at some point... currently it shows only 2.1 and 0.9 megapixels.

but i saw you removed the camera wrapper
[ONE Original Android Development] gondsman:
There is hope in this world! :D
[ONE Original Android Development] renaltosonylevi:
Sounds similar to what I just experienced.

Was running project X then went to restore my nandriod backup omni caf using twrp 2.8.6.0 and all that happened was bootloops On the 1+ screen. I then I restored your 6-14 build and the phone rebooted after about 20 seconds and was very hot and had no sim detected.:eek:

Then I clean installed a regular cm 12.1 build and the phone stayed alive long enough to see that there was no baseband was detected, before another thermal reboot.

To cut along story short I reinstalled twrp 2.8.6.6 and thank god I had made a backup using the efs option.:)
[ONE Original Android Development] Sultanxda:
*makes EFS backup*

In that case... *burns kexec*

It doesn't work like that. Liboemcamera sends the default camera configuration to the camera HAL, and the camera HAL stores this information in an internal array that contains the various camera resolutions and such. The camera wrapper only modifies data as it is sent to the camera service in the ROM; it can't modify an internal array inside the camera HAL. I'd have to make a custom camera HAL for this... which I happen to know how to do :p I got a plain CAF camera HAL to work a couple of months ago, but it couldn't even take pictures (only the camera preview and camcorder worked).

I want to make some adjustments to the camera anyway (such as investigating the overly-compressed JPEG images). I've already spent countless hours researching and reverse engineering the Oxygen camera libraries, so I might be able to get everything to work with my custom camera HAL if I'm lucky.
[ONE Original Android Development] fmc000:
Would you mind telling me which commit did that? Thanks in advance.
[ONE Original Android Development] darkobas:
Updated blobs
[ONE Original Android Development] Sultanxda:
No clue. All I know is that it wasn't the updated blobs, as I ran a build a day before they were uploaded (July 11) and the compass was working.
[ONE Original Android Development] lordsinasina:
Compass is still broken for me. Showing different directions when holding phone vertically and then horizontally.
[ONE Original Android Development] fmc000:
I'm not sure I follow you, sorry. I'm running 0712 build and the compass is not fixed for me. Moreover, there's at least a feedback from a user on today's nightly whose compass doesn't work either. Would you mind pointing me to those "updated blobs"?
[ONE Original Android Development] lordsinasina:
Same reports are going on on cm12.1 thread which people are reporting the compass is still not working properly
[ONE Original Android Development] gborgert:
Wi-fi

What is the difference of configuration wi-fi this ROM for 12S? In my work both ROMs connected in wi-fi, but this ROM appear exclamation point and less stable connection.
[ONE Original Android Development] darkobas:
If you tip it over the 90 degree z axis its supposed to show in opposite direction.
[ONE Original Android Development] andreas__:
Hello sultan. I'm having problems with tethering too. I clean flashed version 09.07 and WiFi tethering didn't work. I updated to 12.07, still didn't work.. 3rd party tethering app reports " couldn't find WAN interface " , cm integration just tells me "error" :D
[ONE Original Android Development] aosp:
In that case... *burns kexec*

[MENTION=3685904]ak[/MENTION] [MENTION=947981]Lord Boeffla[/MENTION]

kexec: Implement kexec-hardboot - https://github.com/andip71/boeffla-kernel-cm-bacon/commit/a04a88e8ccd8d1602d5c76655c73d0f32d29aa35

Implement kexec-hardboot - https://github.com/anarkia1976/AK-OnePone-Reborn/commit/b93c3b7f3a035ed0c02249ba40747c844ad49b3e
[ONE Original Android Development] tarunyad:
Google Voice search forceclosing?

well i tried all Gapps but voice serach force closes on voice commands ... anyone else with same issue?
[ONE Original Android Development] gorunov:
Not work hotspot WiFi in you cm
[ONE Original Android Development] RenderBroken:
Fantastic work on the input boost driver. I was looking over the code and it is very clean and to the point. I may port over (with full credit given obviously) to my non-caf kernel. Also fantastic work overall. Its pretty cool to see what it takes to put together a kernel from scratch. I appreciate the work you are doing. I am sure many others do too.

Is encryption that big of a deal? For me it just seems like wasted overhead. I have alot of friends that have the N6 and they could not stand encryption. I ask this to see your POV.
[ONE Original Android Development] DerRomtester:
Try latest Google search apk http://www.apkmirror.com/apk/google-inc/google-search/
[ONE Original Android Development] AL2000EX:
Yep, hotspot shows error message and breaks WiFi switch until the next reboot.
[ONE Original Android Development] dmarden:
I don't typically use hotspot, but for funsies I tried it on 7/12 (clean flash) and it yielded the same non-working result mentioned above.
[ONE Original Android Development] sychim:
I can also confirm that Hotspot gives the error message.
[ONE Original Android Development] tarunyad:
Still no luck that force closed on me :( !
[ONE Original Android Development] parleyp:
i am having no issues with the hotspot. In fact am tethered to it writing this post.
[ONE Original Android Development] Sultanxda:
Go to Settings -> About Phone. What is your baseband version?

I personally hate encryption too (the government can look at my lolcat picture collection all it wants), but it's still an actual feature of Android. If it's a decision between multirom and an actual Android feature baked into Settings, I'll lean towards fixing the actual Android feature.
[ONE Original Android Development] dmarden:
It's 241.
[ONE Original Android Development] Sultanxda:
Next step: reboot your phone, open up the CatLog app, start recording, reproduce the issue, stop recording, and post/send me the log.
[ONE Original Android Development] 1/4 Life:
We do have something that the N6 doesn't have though -- Qualcomm H/W Accelerated Encryption.

It's a pretty minor performance loss on Bacon, and it's reduced further by using the CFQ scheduler.

I'll switch in a heartbeat once the TWRP issue is solved :)
[ONE Original Android Development] dmarden:
Here you go.
[ONE Original Android Development] dmarden:
Cool, thanks for handling so promptly. I use it very rarely, but I guess it is one of those things where you really need it to work when you go to use it.
[ONE Original Android Development] RenderBroken:
This is a great point. Thanks for taking the time to respond.
[ONE Original Android Development] TimV_:
When I set white as LED notification color the led is blinking pink instead of white any one else having the issue?
[ONE Original Android Development] BitEE:
Yea the led colors are a bit off
[ONE Original Android Development] TimV_:
Thanks for the response.. Is there any idea when this is fixed?
[ONE Original Android Development] PhillyFlyer:
+1 I saw this yesterday. Sadly I stopped reporting issues doe, I think I slipped three bugs on this thread in last couple days but no one has acknowledged. So either its ME or...its me. Yeah, its prob just me.

Anyway I changed the default notification led color to cyan and its working fine. But the untouched default white is def pinkish/purple.

BUT, this is easily the most solid, stable, smooth ROM I've used for my OPO to date and I appreciate the Sultan's work man. I am sticking around.
[ONE Original Android Development] gwindlord:
Not sure what exactly happened, but now everything's working ok. Thanks a lot! :good:
[ONE Original Android Development] Nandeh:
Awesome work!! Best and smoothest ROM tested in the OPO without change default kernel. And by the moment I haven't any touch screen issue.

Thanks!
[ONE Original Android Development] fackamato:
Hey

I wiped all, flashed cm nightly then this on top. Booted, rebooted and flahed gapps for 12.1 from cm. But I don't have the option to add a Google account, only xm account. Reflashing gapps does nothing. Any ideas?
[ONE Original Android Development] sax0406:
Change your gapps.
[ONE Original Android Development] extrem0:
+1. When he still was 15 years old and android1-7. :)

This rom is way far from amazing. Good job, sultan!
[ONE Original Android Development] tan4ik1:
Good job, sultan! :good:
[ONE Original Android Development] fackamato:
EDIT: Solved, thank you

I tried:

gapps-5.1-2015-05-23-24.zip

Slim_mini_gapps.BETA.5.1.build.0.x-20150526.zip

Same results :/
[ONE Original Android Development] feed3:
Wipe system (system only, not data), -> flash ROM -> flash gapps
[ONE Original Android Development] fackamato:
I thought I tried that many times but doing it again worked. Thanks!
[ONE Original Android Development] Sultanxda:
[MENTION=2449407]nazfalas[/MENTION] [MENTION=2504310]Nandeh[/MENTION]

To those of you who had touchscreen issues and now don't have them anymore with my stuff: how is your battery life? Reason why I ask is because I made a funny derp when cleaning up the touchscreen driver, so you might actually be using the new touchscreen firmware that causes the 30mA drain :p What normally happens is that touchscreen firmware is updated every time you turn on the phone, but the firmware updater was broken in my kernel, so my kernel never touched the firmware. Firmware is located on the touchscreen controller and does not disappear after a reboot, so if you were using a kernel that had the touchscreen fix before using my kernel, then you are still using the new firmware with the battery drain from the previous kernel you installed.
[ONE Original Android Development] HaTrED_:
Been trying your rom and enjoying it!

Although, when trying to remove some apps from it, with T. B., like camera, calendar, etc, they just keep there every time.!!

What am I missing?
[ONE Original Android Development] tmimaesk:
Hmm for me battery life is good but I dont know if this is good way to say, but.. I dont find this kernel as responsive as the new touch firmware.. overall the rom is awesome!! Thanks
[ONE Original Android Development] Nandeh:
I didn't say anything about battery life because I had just installed the ROM, but now I can say that battery drain is not present.

I have installed the v0241 firmware, the one what fixed the ghost touches from may15, and even so, the battery life is good.

Thanks!!
[ONE Original Android Development] Sultanxda:
New build uploaded with the notification LED colors fixed and new touchscreen firmware from CM's gerrit (http://review.cyanogenmod.org/#/c/99607/).
[ONE Original Android Development] Renosh:
I had sent you a PM but as suspected the graphic bug is present in your builds too. I wonder how long it'll take CM guys to finally fix the issue. I was hoping so much it wasn't in yours
[ONE Original Android Development] fackamato:
Where's that bug report?

OP: I don't seem to have double tap to wake, or is it somewhere in the settings? Thanks
[ONE Original Android Development] animefans:
Not sure if this is the place to discuss Sultanxda's Omni in this thread...

As I said, I really like Omni. Everything seems to just work

No problem with

4G data (didn't did bandwidth test to confirm), but do see that wonky APN name

wifi tether

adb on PC (can never get that to work under COS12 and CM 12.1 nightly, adb devices show nothing). This is a big deal for me

alarm (CM 12.1 nightly just vibrate, even when sound is set)

apparently better battery performance (got better screen on time even without privacy guard keep awake and wake up toggle, and location set to high accuracy, plus google account syncing turned on)

YAATA chat head dismiss correctly after I reply a new SMS. Under CM 12.1, chat head lives on

Obviously omni rom don't have a lot of features when compare to CM

theme (not an issue to me)

live display (can live without)

notification drawer customization (just do more clicks)

privacy guard (only for the keep awake and wake up toggle. omni's buildin apps ops can manage other privacy settings)

tap and pay (I really want it, but not a deal breaker for me if it's not there)

god knows what else

It's sad to hear Sultanxda does not plan on maintaining his omni. However, I do understand his reason: i would do the same as well

and I have to say: as an 18 years old, you have alot going for you. This is coming from a 45 years old with 3 kids and a full time job in software development (not developer!)
[ONE Original Android Development] om22:
Just flashed and it's the first kernel to get my OPO almost as smooth as my nexus 5 was. Why can't CM itself adjust the CPU boost driver a bit? CM on my nexus 5 had microlags in load spikes and cm on the OPO also has them.

For example: google now launcher swipe to the now page lags if the device is in idle. If you swipe while installing an app or having other load it's smooth. The CM cpu boost driver/interactive governor or whatever (i'm not a dev) isn't sensitive or fast enough to react to short load spikes. Nexus 5 stock used ondemand so it was smooth but used much battery juice.

It's strange that our CPU power (which is plenty) isn't used appropiate to deliver a smooth expirience. This ROM fixes it for me so I have found my new daily driver after trying thousands of ROM/kernel combos with various settings.
[ONE Original Android Development] Sultanxda:
New build uploaded. This build is a bit exciting, as I finally got everything working with the custom camera HAL I painstakingly made from CAF sources a couple of months ago. What does this mean? There are more picture sizes now (such as 9.7MP 16:9), and I've forced the JPEG quality to be 100%, so pictures are compressed as little as possible. Some of my pictures with this new HAL came out between 8MB and 12MB in size.

It's also very likely we lost some fixes from the manufacturer due to the custom camera HAL (as it is based off of plain sources from CAF), so please test the camera thoroughly and let me know how it goes.
[ONE Original Android Development] imam.krismanto:
file is being upload? i don't see new file on download..
[ONE Original Android Development] Sultanxda:
Oops, uploaded it an hour ago but I forgot to update the link. It's fixed now.
[ONE Original Android Development] dmarden:
Not on AFH still. Not complaining, just mentioning in case it is meant to be there.
[ONE Original Android Development] tmimaesk:
It's at the mirror rink
[ONE Original Android Development] bellino13:
I don't see it in either of the links, but it's available from the CM updates in settings.

Sent from Bacon
[ONE Original Android Development] tmimaesk:
http://xdaforums.com/devdb/project/?id=10021#downloads

First file I see is July 13 unless it is time to change my glasses...
[ONE Original Android Development] bellino13:
For some reason when I follow the link to the mirror from the xda app I end up not at a web page, but at my favorites tab of the app. Found an old chrome tab and tried refreshing that, but I didn't see it.

Btw, Wi-Fi tethering works here.

Sent from Bacon
[ONE Original Android Development] tmimaesk:
oh.. well I never used xda app before.. so I guess I didn't know about that..

anyways.. the point is.. it's up :good:
[ONE Original Android Development] dmarden:
Just posting to confirm that tethering is fixed.
[ONE Original Android Development] sneakerspark:
People update about the camera. :)
[ONE Original Android Development] MurikBMX:
After changing the battery indication, "Charging" error "Settings"

sorry for my English)
[ONE Original Android Development] sneakerspark:
Just to confirm mate, by everything you mean clear image, raw, slow shutter etc? :o
[ONE Original Android Development] Sultanxda:
No. Except for RAW, the rest of those features you listed are closed-source.
[ONE Original Android Development] schaggo:
Getting soft-reboots during sleep/idle on 12JUL build. Not sure which log you need to have. Don't think last_kmsg would serve the purpose, hm?
[ONE Original Android Development] ciarpame:
Hi Sultan,

It seems a bit overkill to me, in my experience quality above 95 it's likely to be a waste of space, see here for example: http://www.herongyang.com/Windows/GIMP-JPEG-High-Quality-Levels-Comparison.html (of course this is not conclusive, a better test for us should involve the OPO jpeg compression algorithm and real pictures).

Any way to change this default value maybe editing some configuration file?

How this setting relate to apps with their own setting? (camera fv-5 has a quality setting from 75 to 100, step 5)