yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] adlx.xda:
Search for a post called Clean route to XNP38R in the OPO General Subforum. Don't have the link right now, but Google knows.
[ONE Original Android Development] adlx.xda:
What charger do you use in combination with that cable? I've always charged my OPO with a Galaxy Tab charger (2A) and cable, and I get usually 1300-1400 mA. If you have such low charging you must be probably using a 1A charger, not 2A. Also use the cable provided for a 2A charger.
[ONE Original Android Development] lukesan:
The Opo is very sensitive which USB cable you use.

My advice is to look on ebay and get a charger doctor. The thing costs like nothing and you can see the current and Voltage.

So no more guessing if the cable or charger is ok.
[ONE Original Android Development] dukaiii:
Hi All,

I wanted to go back to the stock kernel. After i flashed the stock boot.img, the wifi stopped working. (Before flashed i renamed the thermal_engine.bak to thermal_engine, but i dont known if this is matters or not.)

Interesting thing is that after this, i flashed back the franco.Kernel r26 and the wifi is working again.

I am on the latest CM 11S 38R.

Someone could help me with this issue?

Thanks in advance!
[ONE Original Android Development] Daedulus Minion:
Franco has mentioned before that you will need to dirty flash the rom if you want to go back to stock.
[ONE Original Android Development] dukaiii:
The whole ROM (33R) or just the update (38R). Because i have tried the dirty flash with the 38R update, but i ended up with the same result.
[ONE Original Android Development] indesisiv:
Dirty flash using the files from here
[ONE Original Android Development] vnphantom:
I just had to roll back to 33R since 38R has been pretty buggy for me. Is R23 the last one that is compatible with 33R?
[ONE Original Android Development] dukaiii:
Thanks, this solved it.
[ONE Original Android Development] Benxter:
I have the same problem....
[ONE Original Android Development] Sanjeev31aug:
Wi-FI Connect and disconnect

Wi-Fi Issue with r26 update, Wi-FI Connect and disconnect very frequently, like every 2nd second.
[ONE Original Android Development] Benxter:
How did you dirtyflash with fastboot? I have the same problem with my wifi after restoring to stock kernel and downloaded the 38R factory ROM and tried to install via TWRP but it fails.

Thanks in advance.

Edit:

fastboot flash modem NON-HLOS.bin

fastboot flash sbl1 sbl1.mbn

fastboot flash dbi sdi.mbn

fastboot flash aboot emmc_appsboot.mbn

fastboot flash rpm rpm.mbn

fastboot flash tz tz.mbn

fastboot flash LOGO logo.bin

fastboot flash boot boot.img

fastboot flash cache cache.img

fastboot flash recovery recovery.img

fastboot flash system system.img

fastboot flash userdata userdata_64g.img

fastboot reboot

But this will wipe my data! Does Dirty flash mean only to flash boot.img and system.img?
[ONE Original Android Development] P1f:
For me is better, in the way that it connects faster to wifi but the signal strength is down, at least by 1 bar if not more. Where i used to have 2 bars before now i get only 1 and this only few meters away from my router.

So maybe if you used to have poor signal before that may be the reason why it disconnects sometimes because now is even worse
[ONE Original Android Development] indesisiv:
Yes just (fastboot) flash system and kernel.
[ONE Original Android Development] dukaiii:
I have not used exactly the stock files. I downloaded a stock rooted .zip (link below) and i flashed it via TWRP. (Wiped only the Cache and Dalvik-Cache.)

http://xdaforums.com/oneplus-one/development/rom-stock-rooted-4-4-4-xnph38r-t2898098
[ONE Original Android Development] V'tino:
I don't know what magic tricks you did, but the WiFi seems to work much better then before. Even if you have 1 bar the speed is still quick..especially when downloading and surfing with weak signals. Nice job [emoji106]

BTW no disconnect issues here
[ONE Original Android Development] Sanjeev31aug:
Wi-Fi Signals are full (4 bars), but it Connect and disconnect like anything.

and Now I have reflash, full Stock Cm11S 38R again. coz when I flashed 38R stock kernel Wi-Fi doesn't turn ON.
[ONE Original Android Development] guitarhero2:
Still getting error
[ONE Original Android Development] V'tino:
Is that on every WiFi router? Did you change also the settings in WiFi advanced menu? Like Region, Frequency and disconnect on low signal?
[ONE Original Android Development] franciscofranco:
OPO is pretty sensitive with the cables/charger used. Dunno if its software limitation or hardware.

I already answered this 1000 times, sorry not writing again.

Yes.

Report to CM.
[ONE Original Android Development] Jeisblack:
Keep UP!!

Great work with the last update!!
[ONE Original Android Development] Peri-:
Best kernel update so far, no issues at all and wifi is much better, thanks.
[ONE Original Android Development] Hzu:
http://xdaforums.com/showthread.php?p=56062039

#shotsfired

Just kidding. Don't wanna start a flame war. Ok maybe I just did. But really, all these talks about governors is interesting. I've been using Android for years and been experimenting with various governors. I still came back to interactive. I don't know why, its just based on my own experience.

Anyway, back to the kernel. Wifi is better now. I no longer lose the Internet connection even when I'm still connected to the wifi. Scrolling is smoother too. Thanks again, Franco.
[ONE Original Android Development] vijacdblz:
I am getting a device not supported error from Franco kernel updater app. Am I doing something wrong.

Installed Franco kernel r26 over 38R.
[ONE Original Android Development] Spannaa:
The free version or the paid one?

The free version doesn't support the OnePlus One
[ONE Original Android Development] vijacdblz:
Free version. Awww am sorry I didn't read it anywhere.
[ONE Original Android Development] Chikko:
I had too,it was a conflict with tasker. I don't know why but deactivating tasker solve my issue!
[ONE Original Android Development] bluedragon1982:
Hey [MENTION=3292224]franciscofranco[/MENTION], i found another issue that only happens with your Kernel, when the device is off and you charge it, there is no charging animation, only a short time the OnePlus Logo is shown, then the screen goes off
[ONE Original Android Development] Tzfardaya:
Known issue, doesn't interfere with charging.
[ONE Original Android Development] franciscofranco:
There are no shots fired, gladly this is a free speech community :)
[ONE Original Android Development] Tzfardaya:
Yeah... They use knives here, not guns.....
[ONE Original Android Development] ramblingpaul:
How long does the first boot after flashing usually take? Been looking at a black screen now for around 20 minutes... (hard buttons are lit)
[ONE Original Android Development] Tzfardaya:
Shouldn't be that long.... A minute tops...
[ONE Original Android Development] ramblingpaul:
Thanks, just tried rebooting, the Android updating man comes on screen for 0.25 seconds then black screen. Looks like I've gone done something wrong. anyone know where I can get the stock kernal from?
[ONE Original Android Development] playya:
did you flash the right kernel? What are you running and what did you flash
[ONE Original Android Development] UyEaH:
:D:D:D hahaha
[ONE Original Android Development] ramblingpaul:
Running Cyanogenmod (CM) 11S 38R (the latest OTA)

Flashed boot-r26.img
[ONE Original Android Development] playya:
I assume the one especially for cm11s
[ONE Original Android Development] ramblingpaul:
Thats correct, the one found here -

//kernels.franco-lnx.net/OnePlusOne/4.4/
[ONE Original Android Development] playya:
OK there goes that theory out the window. Try flashing ROM then kernel and see what happens. Sorry I am not on stock ROM but quite sure if it was an issue you would read about in here. Also have you tried redownloading and reflashing kernel
[ONE Original Android Development] Tzfardaya:
Sounds like a bad flash, redownload and fastboot flash it again...
[ONE Original Android Development] ramblingpaul:
I've tried downloading and flashing again, same result. I've tried flashing the stock kernal back, but it then hangs on the inital boot screen before I enter the encryption password.

2 things that maybe out of the ordinary -

1) the memory is encrypted

2) I am using ART instead of DALVIK.

Starting to get a little worried now :)

Any suggestions are received with thanks
[ONE Original Android Development] playya:
never get worried - did you flash rom then kernel or just flash back your rom to start from scratch more or less
[ONE Original Android Development] ramblingpaul:
All I have done so far is flash the kernal, I've not flashed the rom.

History-

OTA update recieved yesterday

Flashed boot-r26.img did not work

Downloaded and flashed again, did not work.

Downloaded and flashed the stock CM11S Stock Boot/Kernel (XNPH25R) did not work

Flashed boot-r26.img for 3rd time, did not work.

(Thanks for your help so far!)
[ONE Original Android Development] Tzfardaya:
It's the encryption... Franco's kernel doesn't play nice with encrypted devices yet for some reason.
[ONE Original Android Development] Technecium:
Encryption is probably the problem. Search the thread and you should find others who have had issues with encryption, but I'm not sure you'll find a solution.

Art should not be a factor.
[ONE Original Android Development] ramblingpaul:
Thanks, so, any ideas on how to get back to stock? The one on forums.oneplus.net/threads/full-collection-roms-recoveries-kernels.82526/ does not seem to work either.

At this stage I'm happy to lose all data just as long the phone starts working again.....
[ONE Original Android Development] Tzfardaya:
Grab the fastboot files from here and flash boot, system, userdata, etc, etc, etc... (fastboot only, there's probably a zip somewhere that let's you flash stock system from recovery)
[ONE Original Android Development] playya:
curious as I have not had this issue simply because I do not encrypt but have you tried to just wipe and reflash rom. Again, I have not read up on this solution but just asking did you try it
[ONE Original Android Development] kaibosh99:
To the guy with the bad boot issue, is this the same as the one some people have with a stock OPO? There was a story on AndroidPolice a couple of days ago about a magical cure someone had come up to combat it.

For the guy with charging issues, it *must* be the cable. I routinely charge my phone from my computer with a very long, very old cable, and while it is slow (I believe this kernel only supports 400mA over USB/PC) it certainly works. As an aside I too wouldn't mind the 'fast charging' option added at some point, with ASUS AICharger on my pc I can put out 1.8A from my USB ports.

On a similar tangent, for the kernel that my Nexus 7 sports you have both the ability to crank the incoming amperage to 2.6A (bad idea) or better yet to limit the battery capacity to %96. Supposedly capping this increases the number of charge cycles of the battery by %70, pretty crazy and important on a device with a non-removable battery.

ps. Tangent to a tangent, I hope people understand the way battery stats are reported by our devices. I always see people screaming about how bad their battery life is after they have done a full wipe on a device, not realizing that the system needs a fair bit of time to self calibrate - so the numbers are completely out of whack for a couple of days or more if you don't let it drop way down. If you are one of those people that is obsessed with such things, every time you do a full wipe grab one of many free little apps that can check the voltage of the battery, charge it until it is maxed (whatever that is for your device), and then wipe the little system file that tracks the auto-calibration and reboot. The OPO has a scary little feature in that it cannot (thus far) charge the battery while in fastload/recovery, so don't piss around with kernel stuff when you are on an empty tank. There *is* a way to fix it if you fall victim to an utterly dead battery and an unbootable system, thank God.
[ONE Original Android Development] ramblingpaul:
No, I've not wiped and reflashed the rom, I've not touched the rom so far, only flashed the kernal.

I've just started to flash the stock .imgs from here - cyngn.com/products/oneplusone/

---------- Post added at 05:31 PM ---------- Previous post was at 05:15 PM ----------

OK :( I got as far as flashing the userdata and I got hit with this -

unknown partition 'userdata.img'

error: cannot determine image filename for 'userdata.img'

ANy ideas as I now seem to be unable to flash via fastboot.

This has turned into a bit of a nightmare......
[ONE Original Android Development] Tzfardaya:
Just double check your filenames... What size opo do you have, 16 or 64? (unfortunately I'm at work, not at home, I tweaked the nexus flash-all script to work on the opo... But its on the computer at home.)

64 uses the userdata_64 file...

Can you post a list of all the file names in the zip as well, I'll tell you which need to be flashed and which can be left off for now...
[ONE Original Android Development] dayanandgp:
guys, went over last 14 pages and couldn't find anything similar...So here it goes (if its already mentioned somewhere , don't go nuclear over my ass :D)

Flashed r26 and after sometime my Wifi permanently switches off... cannot use the slider to switch it on...just asking since the r26 had something related to Wifi...Restored r25 and Wifi switched on automatically...currently on Mahdi Rom latest build
[ONE Original Android Development] ThommmF:
Encrypted

Since Franco Kernel r22 it is not working anymore.

My OPO is encrypted and I'm on CM11s XNPH38R.

I tried to flash r25 and r26 an a completely new installed system and get a boot loop with a blanc black screen and slightly glimming bottom buttons everytime.

After trying flashing the original kernel back, WI-FI is not working anymore.
[ONE Original Android Development] orangerot.:
There's a new WiFi driver in r26, your rom has to support it, maybe mahdi doesn't have it implemented yet.

This kernel doesn't work with encrypted devices. You have to wait until it's fixed.

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] ThommmF:
Thank you!

But how to know?
[ONE Original Android Development] orangerot.:
I'm pretty sure it'll be mentioned in the changelog...

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] Daedulus Minion:
Don't you have a nandroid backup taken before kernel flash? You can restore that. Will save you all the hastle of complete reinstall
[ONE Original Android Development] kaibosh99:
I am on newest Mahdi and everything is working perfectly.

EDIT: Er, but... http://xdaforums.com/showpost.php?p=56067974&postcount=3348

Mine was working perfectly, though.
[ONE Original Android Development] dayanandgp:
New Mahdi build is up addressing the issue !! :)

http://xdaforums.com/showpost.php?p=56067974&postcount=3348
[ONE Original Android Development] ChefChaudart:
Hi,

Had an reboot while having a video session with Hangouts ;

Cheers
[ONE Original Android Development] Tzfardaya:
Pastie or pastebin plz...
[ONE Original Android Development] BrianAllred:
Looks like the WiFi driver again. Are you on r26?
[ONE Original Android Development] ChefChaudart:
Yes
[ONE Original Android Development] tsiftsism:
Sorry for this post, but i'm outside my home, and i'm writing from a friend's smartphone with limited data plan, so i can't use the search.

My phone just turned off with the battery level [MENTION=5181762]10%[/MENTION].

In the past i had no problem reaching very low battery level without any issues.

Is that a well known issue, was it random or what? If i'm not mistaken there was/were post/s before about this issue before, but i can't remember the answer given, and i can't perform a search this time.
[ONE Original Android Development] BrianAllred:
I'm not Franco, but I bet he'd tell you to report it to CM.
[ONE Original Android Development] Vonnegut:
Red Quote: the obvious question is Explain us in a very technical way why is that. Please, don't waste words talking about somebody else saying so or claiming that's a known remedy. Just stick to the question and be technical, very technical.

If you don't have a clue, just write I don't have a clue...that would be very appreciated.

Green quote: why do you put so much faith in apps that delete the battery history? You can do that yourself...

Blue quote: please explain us that scary feature...in a very technical way and blah blah blah.

---------- Post added at 11:43 PM ---------- Previous post was at 11:30 PM ----------

You clearly wrote the wrong command.

Fastboot (call the program and run it)

flash (the action you want it to do)

userdata (the symlink of the the block mmcblk0p28 you want to flash)

<name of the file> (the image you want to flash the block with)

If you get an error saying cannot determine image filename for 'userdata.img most likely you wrote:

fastboot flash data userdata.img

instead of:

fastboot flash userdata userdata_64.img

So fastboot did tell you the truth..there's not a sector for the userdata.img

As for your bootloop problem, that could be related to the corruption of the persist partition.

If that's the case, flashing this .zip should fix the problem --> http://www.mediafire.com/download/77d5w7yyydkxp7e/Persist.zip

Let's hope that helps you...
[ONE Original Android Development] Tzfardaya:
Red quote, there are databases and caches on the phone that need to rebuild after system changes (kernel install) for example the media server db...

Green quote, He said to use an app that tracks current battery voltage, and to delete the file... Not use an app to delete the file....

Blue QUOTE, this is the first I've heard of it, but given the charge animation while the phone is off, it is possible that the charge circuit can be manipulated via software and have charge disabled in recovery/fastboot and only use then current from USB to power the device rather than charge the battery... It would be the same as having the charge circuit disabled once the battery reaches 100% charge and power the phone from the charger instead of the battery.
[ONE Original Android Development] Vonnegut:
Everything gets rebuilt on boot. Android ask the battery status to battery itself. Android use the battery needed for the tasks. There's no memory and nothing to tweak. Only a mad scientist (or a moron) would write an OS that drains the battery because of a database containing an history.

Just for fun, let's follow this absurd thesis and answer this question: why some ppl claim that after installing a new kernel they experience an above average battery drain and nobody ever claimed the opposite? If there is any memory by the OS, i should expect that scenario too.

In your mind, switching from a kernel with a conservative setting to a kernel sporting a default performance setting should grant 2 days of low batteries drain just because Android is still rebuilding some databases?

Are you kidding or what?

Nope. He talked about app asking for a full charge before deleting the history. Read carefully.

He's right, it's plenty of apps like that on the store...and they are a big placebo.

Why don't you think straight?

Go in fastboot mode and give this command: fastboot oem device-info.

I guess you already did that but you didn't read the output carefully.

As for the recovery, It does recharge the phone.

Please please please check what you're talking about instead of cooking up delusional theories.

If you want to spend all of your time replying to each and all of the XDA users is fine for me.

Anyway, if you want to be useful too, find some more time to play with your OPO and think about matters.

Being responsive and useful is better than being responsive and misleading.

Don't you agree with me on this point?
[ONE Original Android Development] Tzfardaya:
delete please.
[ONE Original Android Development] reeve880916:
Failed to Install Kernel

How do I get rid of the error below when installing Franco Kernel in Recovery mode. The version I was trying to install was R24 and R26.

"E: footer is wrong

E:signature verification failed"

My OPO is all running on stock R38 without rooting. Thank you.
[ONE Original Android Development] Tzfardaya:
Okay, I'll read a little more carefully...

Where did I say that android held a database holding the battery history? Or that they were rebuilt every boot?

I said that there were some system databases, such as media server database that rebuild when there is a system change (and a new kernel qualifies as a system change)

System work in the background (not holding wakelocks) will cause a heavier than normal drain... Depending on how much work needs to be done will determine how long the background process lasts, and how long the additional drain occurs..

Perhaps I misunderstood..

I got the impression he was recommending apps like battery monitor widget which allows you to track the current voltage of your battery... Then deleting the file yourself... And you are right, deleting the file does nothing, it's just a history file, showing what has used the battery, has nothing to do with battery calibration.

Why on earth would I want to think "straight"?

As i said previously, it was the first I'd heard of he phone not charging in fastboot/recovery, and then I postulated a scenario in which case that would be true... Perhaps I'm not the only one who needs to read more carefully?

Yes, describing an existing charge system for lithium based batteries, which may or may not be what this phone uses is cooking up "delusional" theories...

There are two type of charge circuits that can be used..

One uses the battery at all times to power the device, and only uses external power to recharge the battery. (think pass through UPS devices... This will also clean the current and smooth current/voltage fluctuations. And usually used on lead/acid UPS devices)

The second only uses battery when there is no external current, and run the device off external current when available, utilizing any additional current to recharge the battery.. (bypass UPS devices, higher capacity batteries in smaller form factor UPS devices)

The first is hard on lithium based batteries as once the battery is "full" it then constantly drains/tops up the charge... Lithium batteries do not respond well to this "trickle charge" system, and can be damaged by it, reducing both the number of charge cycles available and the duration of each charge.

The second is preferred for lithium batteries, but it s more expensive to implement.

I prefer to be responsive and let people think for themselves, I provide information relevant to the topic, that they can use to make their own decisions.
[ONE Original Android Development] epicnoob66:
Are you using stock recovery?
[ONE Original Android Development] reeve880916:
Yes stock recovery. Volume Down + Power button during phone off. Sorry. I'm truly new to all these. Can you guide how to get rid of this?
[ONE Original Android Development] tmcpnet:
1. Download latest TWRP and save it on desktop. Download latest zip file from Franco and save it on your device.

2. Reboot into bootloader mode, in command prompt run: fastboot boot Name-of-recovery.img

3. Reboot your device.
[ONE Original Android Development] Tzfardaya:
Assuming he's unlocked the bootloader already..
[ONE Original Android Development] reeve880916:
Sorry how do I know whether my device has bootloader unlocked? I didn't done any tweak to my phone before so it would be everything on stock.
[ONE Original Android Development] Tzfardaya:
If you haven't ran "fastboot oem unlock" then it's still locked.
[ONE Original Android Development] jojohnson250:
Great work mate, somehow the device is even smoother to use
[ONE Original Android Development] franciscofranco:
This and stock have the same display colors...
[ONE Original Android Development] weppa83:
but this have the rgb color tuning :D

so i want to make some comparison :D
[ONE Original Android Development] SleemLDJ:
https://db.tt/H6hluGMA
[ONE Original Android Development] phoenixita:
From what i've red This won't work with AOSPA right?