My buttons won't work when i press them not exactly sure whats wrong but this began happening within the past few days. I've been running WTSB 3.5 latest update of 2.4 and Olympus Prime both of which use's a chad kernel which i'm not sure may or may not be the source of the problem. Can anyone offer any suggestions?
Selebrity said:
My buttons won't work when i press them not exactly sure whats wrong but this began happening within the past few days. I've been running WTSB 3.5 latest update of 2.4 and Olympus Prime both of which use's a chad kernel which i'm not sure may or may not be the source of the problem. Can anyone offer any suggestions?
Click to expand...
Click to collapse
By LED buttons I'm going to assume you're referring to the 4 capacitive buttons across the bottom, Home, Menu, Back and Search.
Never really heard of any software disabling these buttons, either intentionally or accidently but doesn't mean it couldn't happen!
Quick shorter term and temporary approach: boot into the custom recovery and see if their lights flash or they work at all in the custom recovery. I remember at one point during TWRP development we had the lights flashing on them. Not sure what kinda support ended up but you should be able to get some type of response to at least indicate the hardware is working.
Long but thorough approach:
Since you are running a custom ROM and kernel, I would suggest first reverting back to Stock and wipe /data and /cache.
If everything works on a Stock ROM and kernel, then you know it has something to do with either the custom ROM, custom kernel or a custom setting configuration. From a known working stock configuration, you can customize one piece at a time checking after each customization step to make sure the buttons work.
Ideally, the buttons will break after a specific customization step and you'll be able to narrow it down to that step and approach the appropriate developer with your results who will then be able to dig into their code and look at the issue.
Hope that helps!
Dalingrin has released a minor update to the cm9 alpha.
Update is in the ongoing alpha thread at Rootzwiki.
http://rootzwiki.com/topic/15509-releasealpha06-cyanogenmod-9-touchpad/
E.E.
Changelogs :
Alpha0.6 Release notes:
Another minor release. While working on bigger problems that will take a while I wanted to push out an update for some things that have happened in the last few days. This is primarily to get Flemmard's work out for more testing. This contains the start of CyanogenMod settings. However, most of the settings are not functional on tablets yet.
With this release I will also provide two flashable zips to allow you to easily switch between lcd density 120 and 160. The default is still 160 because it offers the greatest compatibility. Any lcd density value between 160 and 120 will ruin market compatibility. For those that would like a "higher resolution" look and feel, you may flash the 120 lcd density update.zip. This will copy a new build.prop and will update the launcher for proper display. I strongly recommend changing the font size in Settings->System->Fonts if you chose to do this. The 160 lcd density update is provided to easily revert the change.
Touchscreen fixes
Ability to hide the combined bar(navigation buttons and clock) for full screen. This uses the ICS api so it will require app support(not all apps have been updated). This is an option under Settings->[Interface]->System->Combined Bar (Credits to Flemmard)
Scrollable quick settings. This will require tweaking later to allow it to be bigger on the Touchpad but fixes overflow issue on 7" tablets with the new Bluetooth toggle. (Credits to Flemmard)
Reboot to recovery is working via the power menu(hold down power button). Note: reboot will sometimes shutdown rather than rebooting.
Preliminary support for Rom Manager. In order to use this you will need Rom Manager Premium because it is not official yet. In order to use it you will need to execute "Flash ClockworkMod Recovery" in Rom Manager. Confirm the model is cm_tenderloin, say yes that you have installed manually, and check ClockworkMod 3.x. Now you can use Rom Manager to flash update.zips. Official support should come soon.
Other general changes from syncing with latest changes
Some time ago on a different ROM, my WIFI broke and I've only now found the time to recover/update. Been using an ICS port on my phone and it works far better than any 2.3 ROM. Definitely excited for this.
Im on 0.5 now can i just flash 0.6 through recovery now? Are we at that point yet where we can do this without going through acmeinstaller?
I think there are mixed feelings about going through recovery right now?
TKG26 said:
Im on 0.5 now can i just flash 0.6 through recovery now? Are we at that point yet where we can do this without going through acmeinstaller?
I think there are mixed feelings about going through recovery right now?
Click to expand...
Click to collapse
You've always been able to flash through recovery, even the early CM7 builds.
TKG26 said:
Im on 0.5 now can i just flash 0.6 through recovery now? Are we at that point yet where we can do this without going through acmeinstaller?
I think there are mixed feelings about going through recovery right now?
Click to expand...
Click to collapse
Just like nburnes said, no problem at all.
I did exactly that, without any problems.
E.E.
Thanks just checking..
You should also apply this fix for reboot issues on the power menu where it will shut down instead of reboot. Scroll down to latest release fixes and workarounds.
http://ergh.org/cmtp/
Mike T
classicnerds also released their unofficial version as well
Coming from the simplicity of a Nexus 7 and a Moto G, I am a little confused by how the Z3TC handles recovery and flashing. After a two hour session last night I finally got CM12 20150217 running but not matter what I try, I can't seem to get Xposed 2.7 alpha1 to run (it works just fine on Cm12 on my Nexus so it ought to work, somehow).
In the god awful CM12 recovery, flashing xposed fails with an error message I remain unable to read. Flashing it with the twrp that someone integrated into the stock kernel succeeds according to the twrp status but then the xposed installer still does not see the app_process (it sees the bridge however, which I find weird and have not seen like this before).
So did anyone already manage to cleanly install xposed on a Z3TC? Also, is there any way to get TWRP 2.8.X with CM instead of their awful CM recovery?
In principle, I am open to going to AOSP if someone can point me to a scorpion_windy image (all I can find on FXP is scorpion for AOSP, which is another weirdness that confuses me) and feels I have better chances of getting it to work there....
Hi,
what you need to do is to install twrp recovery to the FOTA partition.
(This will also allow you update cm12 through cyanDelta, which is not possibe with the crappy cm12 recovery)
It's all decribed here: http://forum.xda-developers.com/z3-tablet-compact/development/daily-cm12-unofficial-builds-t2983400
The twrp img is actually a modified Z2 twrp, but it seems to work.
(i am writing "it seems" because i have a SGP621 myself, for this one I can say "it works").
Please note:
- It is no problem if app_process displays only ---, that is a known bug of the alpha
- not all xposed modules are working. XGELS is working for sure, if you want to test.
- You need to invoke soft reboot from within the xposed app after each flashing of the xposed zip (which you need to flash after each ROM update). Otherwise xposed will not work currently.
That seems to have resulted in a (soft?) bricked SGP611. At least now it sits at the Sony logo showing a solid yellow LED and doesn't even turn off anymore (meaning I can't even try to boot it to bootloader to flash a known working kernel anymore)
Edit: Or not, a 10 s power & vol + action followed by power on lets me boot both TWRP and CM12, very strange.
Now lets see if I can get Xprivacy to do its job (for starters, the boot.img contents are different than on the GOogle/Moto devices so we shall see)
nupi said:
That seems to have resulted in a (soft?) bricked SGP611. At least now it sits at the Sony logo showing a solid yellow LED and doesn't even turn off anymore (meaning I can't even try to boot it to bootloader to flash a known working kernel anymore)
Click to expand...
Click to collapse
wow, I'm really sorry to hear that ... I have no idea what might have gone wrong.
You can turn off the device by holding the power button for 7-10 seconds.
If ou want to remove twrp from the FOTA partition, simply reinstall (ONLY) FOTA from the current ftf (SGP621_23.0.1.A.0.167_CE.ftf) through flashtools.
Never mind, I got it back and TWRP flashed xposed cleanly but I can't get it to work - soft reboot does not help, either
However, the kernel seems to have the wrong WiFi drivers for the SGP611 (at the very least, I don't get WiFi anymore). Back to flashing the CM12 kernel for now... I am thinking I should go back to KitKat until someone with a little more clue figures this one out
nupi said:
So did anyone already manage to cleanly install xposed on a Z3TC? Also, is there any way to get TWRP 2.8.X with CM instead of their awful CM recovery?
Click to expand...
Click to collapse
Cyanogen has made the worst mistake every with CM12 and CM Recovery Testing at the same Time.
As long as Cyanogen does not develop a real Recoveryfunction to CM Recovery this crap will block much more then Xposed.
Coming from an oneplus one with cyanogenmod, I really miss the advanced shutdown menu.
Any idea how to get it back ? Specially the reboot options (recovery, fastboot, etc.)
RealLordK1 said:
Coming from an oneplus one with cyanogenmod, I really miss the advanced shutdown menu.
Any idea how to get it back ? Specially the reboot options (recovery, fastboot, etc.)
Click to expand...
Click to collapse
yeah that's one the things I miss from my opo using cos, built in ssh is another, before I'd just open android terminal and ssh form there, but now I;ve to use vx-connectbot or similar. hopefully we'll get a cm bringup for the g5 soon, I know some are already working on it
If you are rooted, I use this https://play.google.com/store/apps/details?id=com.noxx.apm
QuickBoot is free and works good on a rooted G5. However, it's a standalone app and doesn't replace the power menu. It is free.
personally I use twrp app for reboot in recovery...
LineageOS Android Distribution 14
Lineage OS Android Distribution is the continuation of the now discontinued CyanogenMod.
Instructions1. Make a Nandroid backup using TWRP or similar custom recovery if flashing from a different ROM.
2. Download the latest LineageOS ROM (uploading) and copy it to either the internal storage, an SD card, or an OTG usb drive.
3. Download a Nougat (7.1) Google Apps Package (GApps) for ARM devices if desired (OpenGApps recommended).
4. Boot into the custom recovery to flash the ROM and/or GApps .
5. Factory reset if flashing from a different ROM.
XDA:DevDB Information
Unofficial LineageOS, ROM for the Sprint HTC EVO 4G LTE
Contributors
Source Code: https://github.com/LineageOS
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: HBOOT 2.10.0000 or 2.10.5555
Version Information
Status: Testing
Current Beta Version: lineage-14.1-20170302
Beta Release Date: 2017-03-02
Created 2017-01-22
Last Updated 2017-03-02
I'm going find this phone in one of the shoe box and install this thank you kind sir
Wow Los has finally arrived for the Jewel but my Jewel is no longer with me
I can't seems to use external sdcard as internal there's simply no option to do it while formatting. Other then this it's pretty snappy thanks again.
mecha2012 said:
I can't seems to use external sdcard as internal there's simply no option to do it while formatting. Other then this it's pretty snappy thanks again.
Click to expand...
Click to collapse
Thanks for testing! Try the new Nougat build—I wasn't able to move apps onto the SD card (that is a LineageOS bug), but I was able to format it as internal storage.
I couldn't install the latest build 14.1 well just keeps bootlooping at the HTC screen.
Wipe
Install latest build
Install Gapps 7.1 (tried without installing this also) still no go ?
mecha2012 said:
I couldn't install the latest build 14.1 well just keeps bootlooping at the HTC screen.
Wipe
Install latest build
Install Gapps 7.1 (tried without installing this also) still no go
Click to expand...
Click to collapse
There appears to be an error in the build. I will upload a new build within a day.
Edit: New build has been uploaded! Please report if it works.
Never thought my Jewel would ever see Nougat (let alone Lollipop or Marshmallow). Just flashed and all is working well so far. Awesome work!
God tier work here, I'm blown away. I misplaced my Moto G 3rd gen somewhere in my apartment, so I've given up and dusted off my Evo. I was set to just use the Viper 4.1.1 that was on there, but some apps weren't installing so I came on ol' XDA. This is much more than I expected, thank you.
With that said, any tips on getting this to activate on Sprint / Ting? It was working fine on the old rom, but not kicking in here.
I know this isn't totally related to this ROM, but maybe it can be. I'm having issue with this (and most other ROMs I try) where the per button works physically, but only the buttons light up. I have to press the power button several times to get the screen to wake. This isn't consistent though. Seems worse if the screen has been off for a while. Does anyone know of a fix, and if so, can it be incorporated into this ROM? I know there have other threads about this but it seems like they have been dropped.
idumych said:
God tier work here, I'm blown away. I misplaced my Moto G 3rd gen somewhere in my apartment, so I've given up and dusted off my Evo. I was set to just use the Viper 4.1.1 that was on there, but some apps weren't installing so I came on ol' XDA. This is much more than I expected, thank you.
With that said, any tips on getting this to activate on Sprint / Ting? It was working fine on the old rom, but not kicking in here.
Click to expand...
Click to collapse
I believe that the service must be activated on a stock ROM before flashing a custom ROM. Then, the correct APN has to be set according to the carrier under Settings > More > Cellular networks > Access Point Names.
Schiben said:
I know this isn't totally related to this ROM, but maybe it can be. I'm having issue with this (and most other ROMs I try) where the per button works physically, but only the buttons light up. I have to press the power button several times to get the screen to wake. This isn't consistent though. Seems worse if the screen has been off for a while. Does anyone know of a fix, and if so, can it be incorporated into this ROM? I know there have other threads about this but it seems like they have been dropped.
Click to expand...
Click to collapse
I am not sure of a fix, and I have not encountered this issue, but have you tried enabling Wake device using the Camera button under Settings > Buttons?
VitaTaf said:
I am not sure of a fix, and I have not encountered this issue, but have you tried enabling Wake device using the Camera button under Settings > Buttons?
Click to expand...
Click to collapse
I've tried that in the past. Forgot about it this time around. Tried it again and it seems to be about the same as the actual power button for getting the screen to come on correctly.
Good ol' Jewel. Is this rom working ok?
My wife is temporarily using my old Jewel because she dropped & broke her crappy samsung phone. can someone please tell me how this rom is working?
I appreciate your time!
King of the Couch said:
My wife is temporarily using my old Jewel because she dropped & broke her crappy samsung phone. can someone please tell me how this rom is working?
I appreciate your time!
Click to expand...
Click to collapse
The ROM is working fine for the most part. The battery is not great, but that may be due to the battery's age. Additionally, there is a bug with BoringSSL that sometimes prevents the Play Store or Gmail from working temporarily.
sounds good. yeah, I'm sure it's age. thanks man. take care-
Trouble with WiFi
Did a Full factory reset, installed rom, gapps, and supersu from TWRP, factory wipe again from TWRP; now the OS is installed and running but after connecting to my home network, says no internet access although the netork is up and running normally, all other devices connected. Any thoughts or suggestions. I have a backup of my previous state, so I can revert, but would like to keep this on 7.1 for consistency between this and my primary device. The primary use for this device is media streaming.
keysneptune said:
Did a Full factory reset, installed rom, gapps, and supersu from TWRP, factory wipe again from TWRP; now the OS is installed and running but after connecting to my home network, says no internet access although the netork is up and running normally, all other devices connected. Any thoughts or suggestions. I have a backup of my previous state, so I can revert, but would like to keep this on 7.1 for consistency between this and my primary device. The primary use for this device is media streaming.
Click to expand...
Click to collapse
I believe that the WiFi issue have been fixed in the latest build (20170522).
Thank you for this rom!
I had been using cyanogenmod 5.0 and dirtyunicorns 5.1 both were solid roms. Unfortunately the latest apps seem to run a bit slow on them. I thought it was the device but after installing this rom everything is snappy! It manages 1gig of ram better than any other rom and that 1.5ghz dualcore still runs strong. Snapchat is way more responsive on this rom, instagram and fb run without problems. GPS, 4g, sms, wifi, camera, sd storage, everything works! I've only noticed a few bugs. The wifi activity arrows don't show when something is downloading/uploading but wifi itself does work. Also, even tho I have working active cell service, it tries to activate itself again everytime I reboot and fails but calls-sms-data continue to work lol. The biggest bug is that auto-rotation stops working after 30-60 minutes and it stays stuck on portrait mode. Nothing but a full reboot will get it working again, a quick softboot won't fix it. I've tried changing the rotation settings and also added some lines to the build.prop but no solution thus far. I love this rom so much, if it's not fixed I might try some auto rotation apps. One last thing, it would be cool if the # in the status bar would go away after I close whatever app has root. The previous rom I had did that. Thank you so much to all the developers for bringing life to this phone!
familyjewels said:
I had been using cyanogenmod 5.0 and dirtyunicorns 5.1 both were solid roms. Unfortunately the latest apps seem to run a bit slow on them. I thought it was the device but after installing this rom everything is snappy! It manages 1gig of ram better than any other rom and that 1.5ghz dualcore still runs strong. Snapchat is way more responsive on this rom, instagram and fb run without problems. GPS, 4g, sms, wifi, camera, sd storage, everything works! I've only noticed a few bugs. The wifi activity arrows don't show when something is downloading/uploading but wifi itself does work. Also, even tho I have working active cell service, it tries to activate itself again everytime I reboot and fails but calls-sms-data continue to work lol. The biggest bug is that auto-rotation stops working after 30-60 minutes and it stays stuck on portrait mode. Nothing but a full reboot will get it working again, a quick softboot won't fix it. I've tried changing the rotation settings and also added some lines to the build.prop but no solution thus far. I love this rom so much, if it's not fixed I might try some auto rotation apps. One last thing, it would be cool if the # in the status bar would go away after I close whatever app has root. The previous rom I had did that. Thank you so much to all the developers for bringing life to this phone!
Click to expand...
Click to collapse
Thanks for trying out the ROM! The WiFi activity arrows are intentionally disable on LineageOS. I do not currently have an active cell service on this device, so I am unable to fix the activation bug for now. Could you flash the patch below in recovery and test if autorotation is working properly? It should also enable the option to hide the Superuser icon under "Status bar" > "System icons".