yashsingh1/xdaforums huggingface dataset:
[HTC One S] ashvagan:
Update from 10.2.0 to 11 failed

I'm trying to upgrade from 10.2.0 stable to 11 (using both 29-01-14 and 30-01-14 nightlies (dirty flash)) and it's failing. When I go to "Install" in TWRP and select the downloaded CM11 nightly, all I get is failed after a minute of processing. It also messed up with my 10.2 install and I had to restore it from the backup. Any clue what's happening?

EDIT: Please ignore, TWRP on my phone is still 2.5. I think I need 2.6.3 to get CM11.

EDIT: Does anyone know how to upgrade TWRP without using fastboot method? Goomanager says it didn't find any updates for the phone.
[HTC One S] ATSPerson:
You could use flash image GUI to do this.
[HTC One S] deniz2694:
You can use the flash image GUI app here : http://xdaforums.com/showthread.php?t=1045797

you just put the recovery .img in your phone and select recovery in the app, it will flash it.
[HTC One S] Navik57:
Sorry, was busy and haven't been able to get back to this. What happened before when scanning for networks is you would be able to see T-Mobile as an option at least. It is preventing me from roaming, and I know this because I was with another T-Mobile user and they were able to connect to AT&T to roam with no problems.

I think this issue has been in CM for some time, but went unnoticed (really, how often are we using the data roaming?).

Knowing that el smurfo is also seeing the same thing, this puts us back to square one. If I get some time, I'd like to go back to 10.1. I have a feeling the firmware change that happened when we went to 10.2 might be significant.

On a sidenote, I'm also seeing the random reboots when using apps that have GPS. I've found disabling location services helps cut down on reboots (since the phone isn't using GPS all of the time to grab the location).
[HTC One S] kavafree:
Together with intervigil we found what I'm hoping is the fix for the network scanning.

I have been running it stable for one day so far, so I'll probably commit a patch as soon as I get a user who hasn't had any problems to test that it doesn't break anything.
[HTC One S] el_smurfo:
I assume you mean Scan for All Available Networks? I think everyone gets the error, so you might as well post it up for some to test. If you actually mean the signal hopping all over the place, E/3G/H/H+, then I will name my next child Intervigil KavaFree Smurfo.
[HTC One S] kavafree:
Sorry, I'm talking about the scan for all available networks. :P

I'm building a clean build right now, so I'll share the link after some initial testing.
[HTC One S] el_smurfo:
Tempting

http://www.androidpolice.com/2014/0...f-tool-will-unlock-any-htc-device-in-moments/
[HTC One S] nicknc:
Just do it, quit being an s-on wienie. :)
[HTC One S] el_smurfo:
I like to think of myself as more of a retro s-on hipster, too cool to flash kernels in recovery. Also broke, so can't afford a busted phone.
[HTC One S] nicknc:
I have a garminfone I'll lend you. Lol
[HTC One S] Brushstroke:
You haven't S-OFF'd your phone? But it makes things so much easier! :)
[HTC One S] kavafree:
Here's the link (a bit late due to an power outage): http://stiangi.tihlde.org/android/ville/cm-11-20140131-UNOFFICIAL-ville.zip

Worth noticing:

- I can't start the search right after I've booted.

- I get a warning about not connecting to the carrier if I select something else then my regular carrier after I've booted, but it goes away shortly after.

Could someone please test this and reply if it works or not?
[HTC One S] nicknc:
Thanks for the build.

I couldn't get it to boot. Dirty flash over 01/29. Error about no root and then hang at HTC logo.
[HTC One S] el_smurfo:
Meh...I'd like to try a newer radio, but other than that, it's a minor inconvenience. I tried that firewater root twice and both times, it didn't do squat, so I think I'm done bothering with it.
[HTC One S] nicknc:
Gargamel is pleased.
[HTC One S] Brushstroke:
Have you tried Moonshine S-Off? It worked fine for my phone, you just have to be patient.
[HTC One S] provaleriy:
Battery is still might be better. I have an 11% drain over night.

Screenshot: https://www.dropbox.com/s/jaklxvc35adf6k8/Screenshot_2014-02-01-13-05-12.png
[HTC One S] Brushstroke:
So, Trebuchet is now a launcher option with the latest nightly. Honestly, I don't get what's so great about it. I like the Google Experience Launcher. Will anyone start using Trebuchet now?
[HTC One S] el_smurfo:
Just one more non-ROM CM app to replace with a better alternative. I prefer nova launcher
[HTC One S] rootrider:
Historically seen (yeah...) trebuchet was quite innovative the first time it appeared. And many coders of actual launchers (Apex, Nova, Holo, etc.) 'incorporated' its ideas. But there was no futher development and one day even the link to trebuchets homepage was gone. But maybe somebody took over its code for future development and now its back. Whatever...
[HTC One S] kavafree:
Strange. I've been flashing both dirty and clean back and forth between official and my own. Here's the md5, just to be safe: c61759b07ab601ee938fc853011fb858

Is there anything else that could be a problem? I've been following this guide when building.
[HTC One S] noomarsil:
I have a problem with installing apps without using Google Play. It says that 'App is not installed'. What's going on?
[HTC One S] Rapier:
What's the error number you've got?

Sent from nowhere over the air...
[HTC One S] el_smurfo:
I only really get that when trying to install an app that replaces a system app, like the Google keyboard over AOSP
[HTC One S] nicknc:
File size was good, but it could have been a bad download. Will try again later.
[HTC One S] waqypaqy:
Can't seem to find Quick Unlock :(
[HTC One S] sirio87s:
why the photosphere mode doesn't work?? :(
[HTC One S] eabinsan:
So, as a workaround I built myself a kernel with accessory detection disabled. I can boot the zImage just fine, but i can't flash it with fastboot flash zimage (permission denied)

I also tried to build a boot.img, using the current nightly as a base for unmkbootimg and mkbootimg

mkbootimg --kernel arc/arm/boot/zImage --ramdisk initramfs.cpio.gz --base 0x80400000 --cmdline 'console=ttyHSL0,115200,n8 androidboot.hardware=qcom' -o new_boot.img

unfortunately, this just leads to a boot loop :( any advice?
[HTC One S] rootrider:
Yep - there could be a repo update available. Try:

$ repo selfupdate

or redownload and make executable:

$ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo

$ chmod a+x ~/bin/repo

ooops - nearly forgot: change into the right directory first (change if necessary):

$ cd ~/android/system/
[HTC One S] kavafree:
I actually upgraded it some days ago, but to be safe I ran a diff on the newest and the one I'm using.
[HTC One S] rootrider:
There was one about two days ago, if I remember right. So it is possible you caught that already.

If the problem still exists, delete everything from inside the 'out/target/product/ville' directory and restart compiling. Or simply delete the ville directory... :)
[HTC One S] el_smurfo:
Blacklist

Anyone have a trick for blacklisting whole area codes? I almost never use my phone as a phone, so much of my call log is dominated by numbers from Grenada and Caribbean islands...scammers who hang up after one ring in the middle of the night, hoping for a return call they can charge you for. I can blacklist individual numbers, but it's never the same number twice.
[HTC One S] eabinsan:
found the solution, i needed to add ramdiskaddr:

mkbootimg --kernel arch/arm/boot/zImage --ramdisk initramfs.cpio.gz --base 0x80400000 --cmdline 'console=ttyHSL0,115200,n8 androidboot.hardware=qcom' --ramdiskaddr 0x81a00000 -o my_boot.img
[HTC One S] ATSPerson:
Haven't tried this but its looks like it might do the trick.

https://play.google.com/store/apps/details?id=com.flexaspect.android.everycallcontrol
[HTC One S] Brushstroke:
02/02 won't boot for me. Anyone else?
[HTC One S] gannicus84:
Me too
[HTC One S] epsiblivion:
same. and the one time I didn't do a backup. hopefully data is intact (should be) and I can just flash the old nightly

edit: now I'm getting the old no backlight in recovery issue again...

so I reverted to the cwm 6.0.4.5 linked in OP and backlight issue is gone. now reflashed to 1/26 I was running previously. does anyone know if 1/31 is safe to flash? 2/02 is the one that didn't boot. since I didn't wipe, thank god my apps and data still there. I'm on 2.15 hboot
[HTC One S] rootrider:
Same thing with serranoltexx (Galaxy S4 mini, my daughters device) and maybe all/many other devices. Doesn't/don't boot. And maybe it's already fixed. I'll see...

--- edit

The ugly: nightly 2014/02/02 doesn't work

The bad: Next nightly will be working again - but you'll have to wait.

The good: You can download the fix already here: cm-11-20140202-UNOFFICIAL-ville.zip (contains all commits from 'power: Fix locking and reference passing' down)
[HTC One S] Dverez:
Same here, no boot with 02/02.
[HTC One S] sirio87s:
no boot 20140202 nightly! :/
[HTC One S] maluus:
02/02 did not boot for me too. There is also another strangeness happening since the nightlies later than 27/01 (27/01 is the latest without problem). sometimes I could not find out the reason the phone becomes completely inresponsive. screen is off and cannot be switched on, hardware button lights are also off doesn't light up in any case. if enabled notification leds are active. and the phone is actually on. when called from other phone it appears to be ringing but actually it doesn't. And only option to get it off this state is powering down holding power button pressed and power on afterwards. this happened to me all the roms I tried after 27/01. Anyone else is experiencing something similar?

PS: as an another side note although 02/02 did not boot up it seems like somehow switched the phone from ART to Dalvik. When I reverted back to an older nightly noticed it was back to Dalvik.
[HTC One S] F-L-Y-E-R:
Read the comments above, there's already fixed 02/02 uploaded.
[HTC One S] el_smurfo:
I had all of these, no boot, black screen after reverting to 1/31, revert to dalvik flashing 1/31 over 2/2
[HTC One S] nicknc:
And I got some no backlight fun on 31 Jan.
[HTC One S] el_smurfo:
"Fun". Rootriders build seems ok.
[HTC One S] RiffyDivine:
I just flashed this onto my old unit to let my dad use as a replacement for his, but I forgot he had AT&T and not Tmobile. So I put in his sim and now when his sim is in the phone won't connect to anything but if I put mine for tmobile in it will work but both times it asks for the pin unlock code. So I put it in and it will error out on the tmobile network and with the AT&T sim it just won't do anything. Can you not unlock on a custom rom or was there a different radio I needed to flash alongside CM?
[HTC One S] el_smurfo:
You probably need to call T-Mobile and ask them for the SIM unlock code.
[HTC One S] nicknc:
Sim unlock is completely separate from the ROM.

Luckily, the instructions for sim unlock are well documented in a couple of threads in this forum. Pretty easy process with three options to achieve it.

If the unlock prompt is preventing you from using the device itself (it should not be), just boot without a sim.
[HTC One S] Aduck79:
Hi,

I recently got hold of a used htc one s.

I immediately rooted and s-off'ed it. I flashed CM11 nightly and bubba kernel. Then I noticed that the accelerometer didn't work. Tilting in games and launcher doesn't do anything. Do you got a suggestion for what I could do, or is the sensor possibly dead?

Best regards

Anders

Sendt fra min One S med Tapatalk
[HTC One S] MattDN93:
Your sig says you're on HBOOT 2.16. Are there newer nighlies for 2.16 than 20 Jan? I thought all the CM nightlies being pushed are for 2.15 and we're waiting on others to compile for 2.16 separately?
[HTC One S] nicknc:
Lol. 1 broken build and the thread goes silent for hours.

Or it could be everyone is excited about Manning getting his butt whipped tonight....

;)
[HTC One S] el_smurfo:
Hope you put money on that...sheesh. btw, was only broken for a few hours
[HTC One S] nicknc:
Just waiting to see if Denver contributes to the all time high score again.

Lmao.... loving this game!
[HTC One S] The Setlaz:
Got this as well, among other screen freeze and unresponsive hardware button. (running 29/01 nightly)
[HTC One S] nespresso33:
Latest nighlty boot, but no audio anymore ( In call, in playing song, in games etc... )
[HTC One S] nicknc:
It's working for me. Try a clean flash.
[HTC One S] epsiblivion:
have you tried just using the stock kernel?

---------- Post added at 11:17 AM ---------- Previous post was at 11:16 AM ----------

unofficial 2.16 builds are now in a separate thread.

---------- Post added at 11:17 AM ---------- Previous post was at 11:17 AM ----------

clean do you mean wipe data as well? or just system/cache
[HTC One S] Aduck79:
Is the kernel included in CM11 stock kernel? Or can you point me in direction of it?

Edit: Flashed CM11 nightly 30/1 again, without Bubba kernel. Tilting still not working :(

Best regards

Anders
[HTC One S] deniz2694:
yes, the kernel that comes with CM11 is called stock kernel, and you just replaced it with bubba kernel.

To get back to stock kernel you can just reflash your rom or take the .img file in the zip and flash it with fastboot or Flash image GUI app
[HTC One S] Aduck79:
Thanks, tried a flash of CM11 without Bubba. Wiped cache and dalvik. It's the same. Tilting still not working.

Sendt fra min One S med Tapatalk
[HTC One S] deniz2694:
Maybe it was deactivated in Settings > display > rotation ?

I'd suggest you to test with this app if your accelerometer works or not
[HTC One S] speedfreak007:
I'm on nightly 31-01 and my wifi does not always sees the networks available in the neighbourhood. A reboot often solves the problem.

I turned ART on and have no problems with app compatibility and it definitely makes app startups much faster. My one s really flies!
[HTC One S] Aduck79:
Rotation is activated and the app shows nothing at all :( No colored lines.

I'm afraid that the phone could be damaged somehow.
[HTC One S] nicknc:
It's always recommended to do a kernel wipe script between kernel flashes, particularly when you have problems like this.

---------- Post added at 03:44 PM ---------- Previous post was at 03:43 PM ----------

Wipe everything except for data and sdcard. You will have to flash gapps as well.
[HTC One S] The Setlaz:
Just installed 03/02 nightly. Rotation and Audio work fine for me. (I always wipe cache / wipe dalvik though)

The lock-screen unlock black-screen sliding bug is still there :(
[HTC One S] nicknc:
Thanks for ruling that out. Are you experiencing the same behavior with a fresh install of CM11? How about other, non-CM11 Roms? You can always do a full backup and then flash a few alternates to see.
[HTC One S] nicknc:
Impossible. We never have race conditions that lead to unresponsive behavior on this phone.

;)
[HTC One S] el_smurfo:
There does seem to be a spectrum of GPS related issues...I don't have all that many, while some folks just open up Maps and the phone resets. Maybe this guy got the magic phone that the gyro chipset (not sure if same chip as GPS) just never works...and maybe this log will help track down the cause for others. I remember Intervigil said that the GPS problem appeared to the the I2C link to the chip itself, also Panasonic I thought...
[HTC One S] Accountban:
Is there any stable 4.4 rom with no reboots everything I try reboots
[HTC One S] nicknc:
Yeah, that was tongue-in-cheek.

HTC certainly seems to source a variety of parts for otherwise uniform phone series.

It would be useful to rule out a corrupt data setting though, hence the recommendation for a clean install with no data restore.

A number of us had weird issues after jumping up to CM11 due to legacy settings from CM10.2 that were brought in on the data partition.

Most didn't though, I know.
[HTC One S] eabinsan:
to me it doesn't seem to be an I2C issue, even though the logs are full of I2C related stuff. I would say that the real problem is that the device that should be on the other side of the I2C is just powered off. I'm trying to build myself a kernel that does not power of the gyro, just for fun :D let's see how much power this thing really draws....
[HTC One S] epsiblivion:
I'm currently running the 1/26 build of 2.15 hboot official cm 11 nightly. no issues that I can see. recovery is cwm 6.0.4.5 linked in OP

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

can you describe this? I've never seen this before. what happens?
[HTC One S] eabinsan:
seems to be working quite well here....so, if you are not afraid of fastboot and a little power drain (the gyro will not turn off on this build), feel free to test the attached kernel. I tried some multitasking that would previously reboot my phone reliably....but then again, i might just be lucky.

If this works, we hopefully have a very good lead about what needs to be fixed.

oh, and btw: usb accessory detection is also disabled on this kernel. so detecting a dock will not work. i'm just too lazy to do a separate build.
[HTC One S] nicknc:
Yep, this one.
[HTC One S] The Setlaz:
Set Schema or NIP lock-screen for a day, randomly, after unlock, you will have a black/grey screen for 1-2 seconds that seems exiting (sliding effect).

In a day, it should happen a few times (pretty randomly).
[HTC One S] Brushstroke:
Just wanted to report that the 02/03 nightly is running flawlessly. Looks like the camera FC was fixed. :D
[HTC One S] benyto:
What are Schema and NIP lock screen? I don't have those options in my lock screen settings. Are you perhaps referring to PIN and something else? Are you using a language other than English?

For what it is worth, I use a 3x3 pattern for my lock screen security, and I haven't experienced what you're describing.
[HTC One S] Aduck79:
Thanks for your effort!

Tried your kernel. Still no luck I'm afraid.

Compas app not working either, so I think the accelerometer and compas is linked somehow.

From dmesg.log I'm only seeing this related to gyro:

<6>[ 13.943201] [GYRO][PANASONIC] Open device node:ewtzmu2
<6>[ 13.947382] [GYRO][PANASONIC] Release device node:ewtzmu2
<6>[ 13.955837] [GYRO][PANASONIC] Open device node:ewtzmu2daemon
<6>[ 14.097054] warning: `rild' uses 32-bit capabilities (legacy support in use)
<6>[ 14.461803] [GYRO][PANASONIC] EWTZMU2_GetOpenStatus:

And in last_kmsg.log:

[32250.178204] [GYRO][PANASONIC] Open device node:ewtzmu2hal times.
[32250.178265] [GYRO][PANASONIC] Gyro AP on: controldata_active_sensor=0x3
[32250.178296] [GYRO][PANASONIC] Gyro AP on:off_status_hal=1,g_status=0, o_status=0, m_status=1,rv_status=0, la_status=0, gv_status=0,
[32250.178326] [GYRO][PANASONIC] Gyro power off:g_status=0off_status_hal=1
[32250.178357] [GYRO][PANASONIC] Release ewtzmu2hal, remainder is times.

Overall my One S is very stable. Not seeing reboots.

I will try a clean install of CM11 now.

EDIT: Still nothing after clean CM11. Also tried applying the gyro-kernel afterwards. :-/
[HTC One S] thiasB:
already got 3 reboots while playing Ingress today :(
[HTC One S] The Setlaz:
Schema = Pattern

NIP = PIN

Sorry for the bad translation :silly:
[HTC One S] eabinsan:
Sorry to hear that, but my kernel is just supposed to fix the reboots when multi tasking with GPS on (the theory is, that it is not related to GPS but to the Gyro).

But as you get no reboots, this is at least good news for me :angel:

edit: the funny thing about your log is, that it seems to try to turn on the gyro, and the gyro reports back that it is powered off? if this is my kernel, this should not be possible i think.
[HTC One S] Aduck79:
I'm no expert in analyzing logs. Maybe the entries from last_kmsg.log is data from previous boot.

I flashed the PAC-man (4.2.2 android) ROM, gyro not working there either. So, I'm close to acknowledge that the sensor must be dead.

Do you know how to locate the sensor inside the phone? Maybe a plug or something has become loose :)
[HTC One S] eabinsan:
did you try with my experimental kernel?
[HTC One S] thiasB:
Just flashed it. Will report back
[HTC One S] El_Svanto:
I would try to RUU back to stock, and if the problem persists then it is most likely hw fault.

From Sweden btw?

Skickat från min One S via Tapatalk
[HTC One S] nicknc:
+1 to this
[HTC One S] Aduck79:
Ok, will look into it.

Not Sweden but close. I'm from Denmark :)
[HTC One S] El_Svanto:
Almost as good :D

Skickat från min One S via Tapatalk
[HTC One S] djsubtronic:
Having updated from 20th Jan to 3rd Feb (2.16), I have to say the wake lag has really gotten almost as bad as it was during its worst on CM 10.2. On the 20th Jan nightly it had started becoming noticeable, but now it's back to the point where music playback experiences is brief pause/hitch when waking the screen.

:(
[HTC One S] el_smurfo:
Yeah...whatever "fixed" the call screen off bug brought this back with a vengeance...was expecting it and wish it was back the way it was.
[HTC One S] nicknc:
I don't seem to have this. There is a slight delay, but no worse than what is on my wife's lumia (also with amoled).

I am back on bubba, so perhaps there is something there that resolves it.

I did used to get the lag and also the black screen. Glad I DON'T have the black screen anymore.
[HTC One S] djsubtronic:
The 20th Jan build does have the call screen off bug fix implemented, but the screen lag is virtually negligible, and there's no audio hitches. So there has to be something else that's exacerbating the situation. I've reverted for now, can't see any reason to stay on the 3rd Feb nightly. Unless from your experience it has vastly better battery life?
[HTC One S] ATSPerson:
I don't have this wake lag issue at all. When I'm playing music (using Google Music streaming music from the cloud or playing local files) I can use my phone for other things, let it sleep, wake it up whatever with absolutely no lag at all. Using 2.15, 03/02 stock kernel, no tweaks.
[HTC One S] djsubtronic:
The plot thickens.
[HTC One S] Brushstroke:
I also don't have this wake lag issue. There is a very slight lag but its nothing terrible. I'm on 02/03 with stock kernel, hboot 2.15.
[HTC One S] nicknc:
I DO get lag and stutters with some governors. Intellidemand and ondemand both seem to encourage it.

Interactive used to a long time ago, but one of the governor updates [MENTION=4487443]rmbq[/MENTION] pushed to his kernel resolved that.

I use interactive exclusively now, but only on bubba. Perhaps an outdated governor included in stock CM is why the stock kernel performs worse on my phone.

Maybe not though. Either way, I'll stop before papa smurf yells at me for mentioning bubba twice in one day in the cm thread....
[HTC One S] el_smurfo:
Well, there was a bunch of CPU governor related stuff in the last nightly, so maybe that's why it's so bad right now, though if I switch to Performance, the delay is similar. I have noticed the delay since about 1-2 days after the call black screen was fixed...it was fine initially, then there was one more commit afterwards that seemed to bring it back.

Maybe I'll switch to Bubba. Having my phone wake up in my pants all day can't be that bad?
[HTC One S] djsubtronic:
Bubba was awesome when you use an init.d script to disable all those gay2wake options. However, recently it made my phone unstable and battery life was around the same. That's why I insist on stock.
[HTC One S] thiasB:
Your kernel makes me love my phone again - after months of suffering these damn reboots. I encountered not a single reboot when playing Ingress, using other GPS apps and heavily switching between them. Sure, battery drain is higher due to the always-on gyro, but since I have an 10Ah accu pack and power for the chargers almost all day. I'll stick with your kernel until there's a patched stock kernel. Thanks so far!!!

btw: I also love the disabled usb accessory functionality because with stock kernel everytime I've put the phone into the car dock (HTC original) it closed the Ingress app and I had to restart and burn my data plan.
[HTC One S] nicknc:
Lmao
[HTC One S] deniz2694:
You know that you can actually disable all s2w features of bubba kernel with trickster mod app, right ?