Search results

From cm-wifi-off-no-net.log D/ConnectivityService( 551): Setting MTU size: rmnet0, 1500 D/ConnectivityService( 551): Adding Route [0.0.0.0/0 -> 10.129.168.227 rmnet0] to network 106 E/Netd ( 179): netlink response contains error (Network is unreachable) E/ConnectivityService( 551)...

It's possible to bypass Gerrit if you have the permissions. I don't see why it was necessary though. It's useful if you want to push lots of changes or merge commits.

Not a rude question at all. Yes, development from my side has more or less stopped. First it was because I didn't have much time and now I'm lacking motivation. I don't actively use my One X anymore for nearly year. I kept developing because I hoped to get CM 12/12.1 stable relatively quickly...

Thanks. Would you mind doing a test (since you can reproduce the problem) with just CONFIG_NET_SCH_HTB=y? Like Google does it in their base config (https://android.googlesource.com/kernel/common/+/android-3.10/android/configs/android-base.cfg) On endeavoru I just have CONFIG_NET_SCH_HTB...

I'm using it on my grouper and I believe it behaves better than ext4. With the ext4 the device was sometimes unresponsive for many seconds. Now it's much better. But something unrelated could have fixed that but I'm inclined to believe it was f2fs :). Endeavoru could probably benefit from it...

I'm curious. How did you debug this? And how did you end up with the following changes: https://github.com/niker/elitekernel_oxp_kk/commit/d6638409bbbdc7d62bd997dc1039f5534d1871ad Were there some log messages pointing you to it or did you compare configs of different devices?

No time currently as I'm writing and learning for my exams until next week.

Old Layout SD Card Fix Nah, that's not the solution. But I think it pointed me into the right direction. Does the fixed boot.img from https://www.androidfilehost.com/?fid=95916177934536644 help?

Sorry for the broken build with the old layout. Not sure what's going on. Please post a logcat from a boot and the output of "adb shell mount".

Well thanks to you for doing all the support work!

teemo If you have vibration enabled you will notice that immediately. When the phone is off and gets plugged in it boots into the recovery with androidboot.mode=offmode_charging. The HTC choice_fn service looks at the mode and starts the necessary services. offmode_charging or recovery in our...

New build available New build available in both flavors (new and old storage layout). 2015-02-28 Synced with CM Fixed an issue with some SIM cards Fixed USB OTG Fixed broken Wi-Fi after a soft reboot Device encryption should work (make a backup first!) Fixed Rezound Proximity Calibrator

Yes, your phone actually gets powered on when you charge it. It boots into the recovery but should not turn on the display. However the touchscreen is working. So if you have a buggy recovery then you can blindly operate it. I know I fixed a bug related to this for CM 11. But I don't know if all...

Nor does the CM kernel support f2fs. And "converting" might not be what you expect. I'm not aware of any process that can do a inplace conversion from ext4 to f2fs. The partitions are simply formatted as f2fs and you will lose all data in the process. So backups are necessary (as always). f2fs...

https://github.com/thoemy/proprietary_vendor_htc/commit/6a4461859fd5960ab4d730dd63ea5aa834690699 http://review.cyanogenmod.org/#/c/89826/

The PGPSDownloader is only there to download some data that gets send to the nav services. The data is cached somewhere on the /data partition. Look for /data/rxn or something. I don't know why the app constantly checks the connection to the service and to the internet. Probably to spy on us :D.

No. There are some quick and dirty fixes I haven't merged or even uploaded to Gerrit. In this particular case I had to replace proprietary GPS binaries and libraries with ones from another device. It makes the problem go away but I don't know if that causes other problems. I never really checked...

Du kannst wieder zurück zu CM 11 / Sense. Was damit gemeint ist, dass man nicht ohne Weiteres bisher existierende (alte) Recoveries und custom kernels mit den neuen ROMs nutzen kann. Delete the PGPSDowloader app from /system/app or /system/priv-app. Which build are you running? I thought I...

In a terminal as root (there is a Terminal Emulator app, not sure if it's pre-installed) or through ADB. I think selinux currently prevents the execution of the userinit script. Check if it's still the case if you execute the command manually.

But we have to fix it because grouper doesn't use the partition footer for the encryption keys. See http://review.cyanogenmod.org/#/c/88915/3..5/recovery/root/etc/twrp.fstab,cm

I have enabled the bug reports for this project. If you reported something please do so again there to help me (and others) keep track. Thank you!

I tried to reproduce that with my BT headset. Played music with Google Play and sent a Pushbullet notification to the phone. The music volume was decreased for a short moment for the notification and went back to normal after hat. No breakage. I need more information. What apps are you using...

Well the app requests root rights. And we try to not confine root too much because it would render the root rights useless. Maybe the app handles the boot event differently.

That shouldn't work. SELinux blocks access to the proximity sensor file even though the App requests root. Can you look at the/data/misc/audit/audit.log file? Maybe it was fixed. I haven't tested the App since a while.

The data source is empty: https://github.com/CyanogenMod/android_frameworks_base/blob/cm-12.0/packages/SystemUI/src/com/android/systemui/media/NotificationPlayer.java#L122 NotificationPlayer.play() is called here...

It shouldn't break anything. So everyone can install it. But it is primarily for users that have problems.

I've noticed that if /data/media/0 exists TWRP will return the contents of that folder for the Internal Storage MTP device. That's the "default" and also what Android itself will show. But after a fresh format of the /data partition /data/media/ did not exist and it did display the contents of...

Thanks for the link. I added it to the FAQ. FYI I always did what's described under "Option 2" and never had problems with it. I really need to check what's up with 1 & 3. I can enable S2W in the settings and have no problems with the screen dying. I upload more or less the same builds I...

Unfortunately your logs aren't too helpful. Simply too much happening and I don't know what. When you have the problem the next time can you post the output of "ip route" and "netcfg"?

Yes I'm aware of that. My plan is to provide builds with the old layout until there is a good enough CM 12 build. People coming from KitKat should be able to easily and properly test CM 12 before making the decision more ore less final. But those builds won't be tested by me and the remaining...

Can this app also create a radio log? Something starts to happen around 01:59:55. But I don't know what.

vinylzero successfully tested this fix https://www.androidfilehost.com/?fid=95916177934529711 Rename it and replace the file /system/framework/telephony-common.jar See: http://review.cyanogenmod.org/#/c/88932/

The recovery uses a kernel with a outdated F2FS driver and can cause corruption in combination with the kernel used by CyanogenMod.

Are other ROMs (including stock) better?

Kernel is 99.9% CM. There's one change to it but that is completely unrelated. Good to know. Are other people still have problems with calls and mobile data? Because there is indeed an issue with SIM cards that don't have a ICCID (or Lollipop is unable to read it). Since Lollipop supports...

Meh. How long do you have to wait after a boot? Because I cannot reproduce it. sweep2wake is enabled. I rebooted and didn't touch the phone for 5 minutes. Touch screen still works.

The original /data partition is left untouched should still contain you old data if you haven't formatted it. But your SD cards needs to formatted to vfat again. To go back you install an old recovery, format the SD card to vfat and flash a old ROM. No need to restore a backup. Please get me...

No idea sorry. I haven't been using my One X to make phone calls since a couple of months. But I never had problems like that with CM 11.

New build available 2015-02-14 Uses new storage layout. Read post #3. New boot.img and a complete wipe is required! Synced with CM Maybe working Google Play Movies

Unfortunately not. Do you have swipe2wake enabled? I need a log for that. There a problems with Wi-Fi similar to that with several Lollipop devices. So it's not CM and probably also not device related. But logs are always helpful. No idea what you mean with app processing mode "interactive". I...

Oh right. From a technical standpoint it could work in theory. But the recovery will actually complain that tilapia != grouper when flashing a ROM. Or similar issues. Will remove the link.

Here's a CM compatible TWRP 2.8.5.0 recovery: https://www.androidfilehost.com/?fid=95916177934528848. It's actually build for Grouper but could work on Tilapia. Corruptions should not happen with it.

CM compatible F2FS recovery I've uploaded a CM compatible F2FS recovery (TWRP 2.8.5.0) here: https://www.androidfilehost.com/?fid=95916177934528848

Using it for dalvik cache is risky as the cache may be able to grow beyond 2GB. Unlikely but possible.

Most changes are in the ramdisk and Sense developers can change that easily. But there's one change in a framework XML file. But I think it's possible to change that also by decompiling the framework.jar. Ask your favorite Sense developer what he/she thinks about the change. However there's a...

I can confirm that. But you have to be very cautious. I think all currently available F2FS recoveries are not recent enough for the F2FS version used by the CM kernel. This can result in a corrupt /data partition and possibly complete data loss when you reboot into the recovery after using CM...

I need a log for this. Pretty sure it worked on my device.

How long did you wait? The first boot can take a while (2-5 minutes).

Because it's not actually double-tap to wake but instead swipe to wake. There's currently no double-tap to wake functionality in our kernel.