yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] damageboy:
No 3g data?

Is there a chance the 061GOLD is mucking up my 3g data?

I upgraded to 61 this morning from 60 and I pretty sure that 2 the last time I saw 3g data working

Dies anyone have a link to a stock 38R zip I could use to verify this using twrp?

Any other ideas?

Wifi works fine, so do 3g phone calls
[ONE Original Android Development] DerRomtester:
I am using 4.9 linaro with -O3 and i have no problems so far.
[ONE Original Android Development] kouss77550:
Does this kernel has ULPS enabled?
[ONE Original Android Development] leafs44:
Yes
[ONE Original Android Development] dy2592:
So I just had my phone reboot by itself and it deleted and erased everything on my phone. The system data and storage data. I was greeted with the first time setup screen =/. Super bummed as I just got finished setting up and installing everything.

Im on the Manhdi Rom so Im not sure which is the cause. I post over there and thought I should too here so if anyone has encountered this before or has any suggestion to possible try to avoid this the next time, much appreciated.
[ONE Original Android Development] DJMartini:
Search this thread... I just posted about this with same issue. I was able to find my data. Just had to get it from adb pull and fix my corruption emc.
[ONE Original Android Development] ak:
What recovery and rom?
[ONE Original Android Development] nicholaschum:
@ak, there have been reports that sound stops working on a new ROM commit in Mahdi, will there be an imminent release for sound commit released in the next nightly?
[ONE Original Android Development] hari623:
No Audio, BT works tho

I have the same problem.

Currently using Mahdi, twpr, ak61.
[ONE Original Android Development] dy2592:
Hi AK,

I am using twrp and Mahdi rom. Both the latest, the latter being 2.8. I've recently just completely wiped and flashed the rom again, but this time I reverted back to your 0.50 kernal. I am afraid to have this happen again as I lose everything on the phone and no option to even at least backup my data. scary.
[ONE Original Android Development] ak:
The problem isn't the kernel .... I'm using twrp 2.7 without a single problem .. Any kernel is the same from time begin.

Sent from my A0001
[ONE Original Android Development] ak:
What is the ROM version?

Sent from my A0001
[ONE Original Android Development] nicholaschum:
Mahdi 10/10
[ONE Original Android Development] ak:
Yes I have to merge last CM

Sent from my A0001
[ONE Original Android Development] ak:
This is impossible ..

Sent from my A0001
[ONE Original Android Development] ak:
Wow ... How is possible ? [emoji15]

Sent from my A0001
[ONE Original Android Development] ak:
Test

Today I did a test to try to understand why and if it is reproducible side of my various problems with the partitions.

My setup is:

038R fresh install with wipe of all partitions

twrp 2.7.1.1

latest ak kernel (v061 CM Version)

ext4 format

Test:

Overclocked phone to 2.8G and Undervolted -125mV

Step:

I took the phone to the phase

of

crash for 6 times

Conclusions:

I never had problems with partitions

I'm available to see if anyone has ideas how to reproduce the problem and how it can be inputabile to the kernel.
[ONE Original Android Development] jgcaap:
Which bug bro?
[ONE Original Android Development] prstorero:
Where the phone crashes and data gets erased. There's a couple posts about it within the last 3-4 pages I believe.
[ONE Original Android Development] jgcaap:
Never had this...
[ONE Original Android Development] Setting.Out:
From what I've read, everyone who has had issues it was with twrp (2.7.0 and 2.8.0).. I use an unofficial twrp (2.8.0.1) and don't face this issue.. Also 2.7.0.1 never caused issues either.. When I used 2.8 I lost my imei and suffered from massive reboots but no other data loss..
[ONE Original Android Development] OmegaBlaze:
2.8.0.1 made me lose my imei and wifi. Internal storage as well. I can't **** with twrp after that ordeal.
[ONE Original Android Development] Laum:
With latest Cm nightly (also 09 version) some sounds do not work, for example alarm and ring volume adjustment sounds. With stock kernel they are fine.
[ONE Original Android Development] ak:
Correct its normal, because i dont have merge last commits.
[ONE Original Android Development] Laum:
Thanks ak!
[ONE Original Android Development] jgcaap:
reading today this and testing (at the computer now :P )

---------- Post added at 10:21 AM ---------- Previous post was at 10:00 AM ----------

guys anyone having flickering graphics or ghost touches, please read here to help me on my research:

http://xdaforums.com/oneplus-one/general/ghost-touches-flickering-graphics-t2900756
[ONE Original Android Development] rickyx32:
Fellas, what's the reason for this? I'm coming from a fresh install of everything.
[ONE Original Android Development] NickosD:
Search!
[ONE Original Android Development] ak:
can you Post on UKM thread please?
[ONE Original Android Development] rickyx32:
Aye captain...
[ONE Original Android Development] funCrash93:
so [MENTION=3685904]ak[/MENTION] what about latest CM.?

do you have a nightly build for this GOLD one.?

how to solve this lack of sound.? (tho Media Sound works, like Google Music plays songs, but Ringtone/Notifications are dead) :/

MAHDI 10/09 w/ GOLD61.
[ONE Original Android Development] DerRomtester:
Lack of sound is because of a new kernel commit from cm. When ak releases next version he will merge cm upstream and your sound is back.
[ONE Original Android Development] ak:
You can check my site, a surprise.
[ONE Original Android Development] funCrash93:
yes, I know. That's why I asked about a nightly :P

---------- Post added at 03:49 PM ---------- Previous post was at 03:49 PM ----------

checking now :finger-crossed: :)
[ONE Original Android Development] ak:
Its official, no time for update XDA.
[ONE Original Android Development] funCrash93:
Thank you :)

already in Recovery & flashing ;)

---------- Post added at 03:55 PM ---------- Previous post was at 03:52 PM ----------

Sound is back :)

Thanks again for a GREAT Job ;)
[ONE Original Android Development] cd69:
Sound working. All good so far with mahdi latest. Kudos and thanks ak ?

Oneplus Nexus 5
[ONE Original Android Development] Jole7:
Hi my friend! I had the same problem with 060 cm11s version i flashed 061 cm11 and solve that.

---------- Post added at 03:10 PM ---------- Previous post was at 03:00 PM ----------

Fellas, what's the reason for this? I'm coming from a fresh install of everything

Hi my friend! I had the same problem with 060 cm11s version i flashed 061 cm11 and solve that.:)
[ONE Original Android Development] DJMartini:
I don't use TWRP recovery when this happened to me. I actually use CWM Advanced 6.58.0 ... I'm Undervolted at -100mV, but never overclocked. Just happened to me once though.
[ONE Original Android Development] drbest:
Overclocked phone to 2.8G and Undervolted -125mV

What a terrible combination (overclocking und undervoltage)! And then you are wondering that your Hardware is not functioning well - LOL :confused::eek::D

I think, if you choose the extrem 2,8GHz setting of the AK-Kernel you have to increase the voltage, but it´s really not to recommend to do this.
[ONE Original Android Development] RobbieL811:
This is exactly what I was talking about w/ undrevolt the other day. Undervolting ONLY creates instabilities! Does nothing else.
[ONE Original Android Development] ak:
Holy words.
[ONE Original Android Development] ak:
new kernel online

[AK KERNEL - GOLD ED. - V.063]

A kernel based on CAF CM11 Bacon branch.

for ROMS > 038R > CM11S: AK.63.GOLD.OPO.CM11S

for ROMS > 20141010 > CM11: AK.063.GOLD.OPO.CM11

[SMALL CHANGELOG]

updated to the last CM source

reverted some commits for stability purpose

improve msm limiter

expose PVS level to sysfs

added bool for disable kernel logging

ecc

[FULL CHANGELOG]

Project name: AK KERNEL
anarkia1976 - Kernel Version: AK.063.GOLD.OPO.CM11
anarkia1976 - Revert "mm: Adjust dirty writeback for IO boost"
anarkia1976 - Revert "fs: dcache: set vfs_cache_pressure 40%"
anarkia1976 - Revert "fs: Add sysfs module to allow enabling/disabling of fsync"
anarkia1976 - ak_bacon_defconfig: enable PVS_LEVEL_INTERFACE
andip71 - clock-krait-8974: Expose PVS level via sysfs
andip71 - random: increase entropy levels (both read and write)
anarkia1976 - ak_bacon_defconfig: Add xbox controller support as module
anarkia1976 - ak_bacon_defconfig: Enable USB OTG Ethernet support (as modules)
andip71 - printk: Add sys kernel interface to configure linux printk logging
anarkia1976 - Kernel Version: AK.062.GOLD.OPO.CM11
Pranav Vashi - msm: limiter: Improve routines
Steve Kondik - msm8974: Add ultra-low-latency audio instance
anarkia1976 - Revert "drivers/power/qpnp-charger.c: fix charging issues with non-Oppo chargers"
anarkia1976 - Revert "drivers/power/qpnp-charger.c: add back dropped aicl control"
[ONE Original Android Development] magnamentis:
cannot confirm

normally i don't post things like that since it simply can happen from time to time but since more and more people are reporting data loss i at least want to confirm their issue, it happened to me a few days ago that a random reboot which is very rare on all my devices and after that i was greeted with the first time install screen ( account setup, wifi setup etc. ) and had to go from there. happened on my one plus one with cm11 and ak kernel and xposed framwork plus a few reknown and usually trouble free modules.

point is in reply to your post, that i'm using clockworkmod recocvery not twrp. so it CAN happen with other recoveries while else i concur with your observation that twrp 2.8 has been the mostly used recovery in those cases when it happened, but this can be a coincidence like the whole issue itself.

only thing i could ad is that when i heard that certain tweaks and settings are going to find their way into default kernel settings i expected something to change. reason is that in the beginning i was testing and tweaking heavily on this kernel myself just to find out what's going to happen and what are the benefits and issues. result was that i ended up with similar problems, some very strange things and after that decided to go with more conservative tweaks to make things a bit snappier.

IMHO whenever the battery usage which is already good wants to be pushed to the limits sooner or later users face all kinds of issues hardly to proof even that they are related. best example is franco who 2 or 3 times a year almost starts from scratch ( super clean ups ) when things get out of hand. the best way to go is like [MENTION=4684315]flar2[/MENTION] is doing it. his kernel for example i have for almost a year installed on my nexus 5 and there are simply no issues and at the same time very good balance between batt-life, performance and stability.
[ONE Original Android Development] RobbieL811:
What does "magnamentis" mean? You are an author? I see in your sig, a link to a website referencing a book? Did you write this?
[ONE Original Android Development] flame360:
Hi AK! I believe the problem is caused when the phone crashes while writing to SD. I saw that someone else besides me also had this when the phone crashed while doing a titanium backup.

May I suggest you to do a titanium backup plus download one or two big files at the same time and then make it crash.

For the record I was using Phil recovery when this happened
[ONE Original Android Development] DJMartini:
Think you should re-read what I stated "never overclocked" ... It's pointless to OC and UV same time. In fact vvvvvvvv (exactly what Robbie says)

I'm beginning to think that UV is pointless anymore myself. Your ROM with ak stock settings actually works great and battery is still better than CM11S stock kernel.
[ONE Original Android Development] magnamentis:
uhh... smile

answered through pm :)
[ONE Original Android Development] ak:
If you have this type of crash its normal to fck up your SD partition.

Sent from my A0001
[ONE Original Android Development] magnamentis:
have to agree loudly. posting issues with undervolted devices should be prohibited ( against the rules ) the threads are full of such and similar cases while everyone with a nandroid should just be able to go one step back and retry without causing devs to sweat each time they overdo and fail.
[ONE Original Android Development] RobbieL811:
Well, it is kinda frowned upon to report problems w/ undervolt applied, but not all users might know this. The user reporting the problem may not have known he was doing anything wrong.

To the user that reported the problems, go back and see if the same things happen w/ stock voltage and stock clock speeds. I forgot your name lol. Sorry.
[ONE Original Android Development] EasyGoingXD:
Fast Charge at 2000mA?, isnt that dangerous?
[ONE Original Android Development] ak:
No because this is the normal max amp of your charger when you connect your phone.

Sent from my A0001
[ONE Original Android Development] EasyGoingXD:
Why does the information-point say that the MAX is 1500?

And its also net dangerous for the battery/phone itself?
[ONE Original Android Development] magnamentis:
no

as [MENTION=3685904]ak[/MENTION] explained.

further this i a veeerrryyyy old setup from 0.39 a lot has changed since then. some of the settings were to improve touch responsivness

which in the meantime got better and the kernel as well developed further since then.

no more but only partial OV and noop instead of row etc. etc.

i posted a few pages back a more detailed explanation about charging voltages and amperages. this will make it even more clear

amperes are the amount of power available and are sucked from devices not pushed ( not like turbo engines but more like atmospheric breathing engines ) while the voltage is speed and pressure and this can damage your device or melt wires. ( even put your stuff on fire hahah.. )
[ONE Original Android Development] akarol:
AK, how come Fast Charge and max amperage is not maxed out by default?
[ONE Original Android Development] stab244:
Because not all people have devices that support it? Imagine not knowing that was the default and plugging in your phone to your computer only to mess up the USB port on your computer because the phone drew too much current. Not very many happy users would result from that.

Sent from my bacon
[ONE Original Android Development] EasyGoingXD:
So....is there a big risk to mess up my oneplus using fast charge at 2000mA at the wall charger?
[ONE Original Android Development] RobbieL811:
[MENTION=3475639]ak.[/MENTION] I just updated sm-arm-eabi-4.8, and sm-arm-eabi-4.9. Idk if you still track these toolchains, but there is an update to them if you wanna grab it.
[ONE Original Android Development] ak:
Thanks a lot my friend.
[ONE Original Android Development] ak:
Example:

if you attached your phone to usb 2.0 and you have set 2000, your max ampere is always 500 (max usb output).
[ONE Original Android Development] ak:
Because i don't want people that point to me a finger and blah blah blah. so you can make your free choice.
[ONE Original Android Development] EasyGoingXD:
and where is the mind of setting 2000? ^^
[ONE Original Android Development] DJMartini:
Yes, there is always risk in charging any battery over what it's recommended/designed mA charging rate is designed for.

DC is different than AC. Our phones are recommended to accommodate a 2000mA charge (based off what we're getting from AC unit charging). DC charging (normally USB) is < AC charging. Some AC chargers by designed have small transistors that won't allow additional mA's to be pushed or it can damage the charger itself. DC is different normally pushing lower mA's to conserve energy for other things..

All fast charging is doing is allowing us to increase mA's up to 2000mA (what our phone allows). Technically, we could push this and shouldn't cause any harm to our phone, but longer/slower charges tend to make batteries last longer than quicker/higher mA charges.

If you search on google you can find all about this. They actually have interesting videos showing how we could charge batteries less than a minute to full capacity, but the longevity of the battery is worthless. We'd have to replace a lot more often.
[ONE Original Android Development] ak:
with this you can bypass hw control and make fcharge always ... even if the device is recognized like USB chargingv(limited to 500mA).
[ONE Original Android Development] EasyGoingXD:
Now i am getting it thank you very much :) I will stay at 1500 :)
[ONE Original Android Development] funCrash93:
[MENTION=3685904]ak[/MENTION] what have you changed about PVS that Synapse doesn't show me the number for that and BIN.? :confused:

Send from my bacon.
[ONE Original Android Development] EasyGoingXD:
Thats why i am using Sensei's Kernel (based on AK with fast charge) because he removed it :/
[ONE Original Android Development] DJMartini:
Like ak said most USB charges at 500mA ... I myself use and push at 1500mA and have for sometime on majority of my phones without problems. I'd say you're pretty safe running at 1500mA.

Thank you [MENTION=3685904]ak[/MENTION] for keep fast charge as an option too!
[ONE Original Android Development] funCrash93:
BTW, about this Fast Charge thing. I have an external battery that has two operational modes (1A and 2A for choice of output)

as you all people know, our phone has a default charger of 2A (2.1A EU), so that means 2A is absolutely safe and recommended.

so about my story, knowing the above things, I've set fast charging to 2A in Synapse (as even if I use my external battery at 2A output mode, it would not give that much, dunno why) and after that the phone charges faster with my external battery BUT even though the phone "feels" ? cool on that Amperage my external battery goes very hot (I guess the phone "sucks" power on full speed and my battery can handle.

So if you are using an authentic device for charging that is capable to provide 2A of output that setting fast charging to 2A is OK (it won't affect the phone in any ways), but if you are using a device that can provide 2A only "on paper" (like mine) than, allowing the phone to "suck" the power out of a charger with this among can hurt the charger (my case, got very hot).

p.s. guess this post went to long :D

sorry if something is not much clear in my explanation as my native language is not English, or if a word is misplaced (or letter) than it can be because of TouchPal's Swype recognition :P

Send from my bacon.

---------- Post added at 09:54 PM ---------- Previous post was at 09:52 PM ----------

latest AK has Fast Charging.

I asked about something else.

Send from my bacon.
[ONE Original Android Development] EasyGoingXD:
Thank you again :)

Latest AK hast Fast Charge enabled again? (10/10 version or 08/10?)
[ONE Original Android Development] gianton:
[MENTION=3685904]ak[/MENTION] My OPO is on its way to me from the US, can't wait to try your latest work mate!
[ONE Original Android Development] funCrash93:
check the logs.

as far as I can remember [MENTION=3685904]ak[/MENTION] enabled that from version 61 and up.

63 has it for sure :P

so update your ROM and flash 63 ;)

Send from my bacon.
[ONE Original Android Development] EasyGoingXD:
Have to mod first the newest Mahdi Rom to F2FS ;)
[ONE Original Android Development] :
Error when i flash kernel in multirom with cm11 m11
[ONE Original Android Development] ak:
Wow another good friend on the way ... welcome into the OPO family. ;)
[ONE Original Android Development] druweed:
yup same issue here, latest multirom, using ak63 for CM11S
[ONE Original Android Development] ak:
Because I have forced a check for bad repack of ramdisk. So you have to post log during the problem ... Related to recovery session. Can you try with official twrp?

Sent from my A0001
[ONE Original Android Development] akarol:
Got another hang/reboot today. Right when I ended my call. It just hung with the black screen for a while until I gave up and forced reboot. Any way to get a crash report?
[ONE Original Android Development] NickosD:
Actually guys, the thing where we lose data on reboot it could be a rom problem. Happened and with boeffla kernel.
[ONE Original Android Development] magnamentis:
quite easy to find out

so everyone with data loss should post his rom and we'll know whether the roms have something in common:

i'm on cm11 always latest nightly no dataloss on other 5 devices with same rom and config, only device where it happened was oneplus one

this does not assume anything, it's a simple statement of facts as to which rom kernel config was installed when it happened.
[ONE Original Android Development] Rindermulch:
How to update

Hello everyone,

I'm pretty green when it comes to custom Kernels.

My question is, how do I have to update the ak Kernel?

If i would want to update from v.060 to v.063 would I have to go from v.060 to stock Kernel and than to v.063 or v.060 --> v.063 or v.060 --> v.061 --> v.062 --> v.063?
[ONE Original Android Development] NickosD:
60->63

---------- Post added at 01:35 AM ---------- Previous post was at 01:35 AM ----------

I suppose we all the in common the 38r rom.... First time happened to me was after flashing the update.
[ONE Original Android Development] Soul0Reaper:
What exactly does interactive_pro do differently than interactive?
[ONE Original Android Development] magnamentis:
no

no offense meant but you should read :) "smile" i wrote that i'm on cm11 latest nightlies on 6 devices and none of them has a cm11s rom installed, neither r38 nor any earlier version, so that's would seem to be the opposite of in common as far as rom is concerned, but would still leave the kernel in commone considered the most probably people in this thread are using or have been using this kernel.

changing to another kernel does not automacially mean that all residues are wiped, same would apply to changing roms but i never changed roms in the past 8 months other than from whatever was before > to cm11 nightlies. and as i said did not happen on any other device except n7100 in march and it was agni kernel messing up partition and at that time it was admitted by the dev who came up himself with the solution so that it would not happen again. that's the history, again without making any assumptions.

so my proposal was that each one simply states facts, which rom and kernel was installed and leaves the rest and any assumptions up to those who think the information might be useful or perhaps not.
[ONE Original Android Development] jgcaap:
Dam :/ is there many users with this issue? So strange.
[ONE Original Android Development] chachin:
i been liking all the updates [MENTION=3685904]ak[/MENTION] has made. i dont have reboots, no nothing bad.all awesomeness. all we need now is for kernel.org to upate to 3.4.105 since it's been ages :P

btw thanks 100x again [MENTION=3685904]ak[/MENTION] :):D:D:D
[ONE Original Android Development] noregretzzzz:
I hope this post is of some worth if I can at least help one person. Regarding the data loss, that only happened to me once on the galaxy nexus and I feel it was because I had turned off fsync. Always made sure to have fsync on after that and never happened again. Maybe that could be a potential cause?
[ONE Original Android Development] Evermind10:
If I'm not wrong the option for fsync is removed in v63. I dun see that option in synapse.
[ONE Original Android Development] prstorero:
I believe that's correct. Since things wouldn't get written when a crash happened, that's the most likely cause. I think everyone that had the issue was linked to fsync.
[ONE Original Android Development] clock51:
are in MultiROM, 063 cm11 with slimsaber and crdroid everything ok, 063 38R 11s with CM11S rom error "failed" 061 cm11s all ok
[ONE Original Android Development] ak:
Thanks a lot for report.

I think users with this problems is related to fs ext4 corruption.

the best way is to run e2fsck on data partition.
[ONE Original Android Development] ak:
As always:

- rom

- config

- kernel ver

- last kmsg

- ecc ecc ecc
[ONE Original Android Development] funCrash93:
why mod.?

MAHDI supports F2FS w/o modding, no.?

Send from my bacon.