Related
Originally Posted by Awassenaar
Hello everybody!
Since friday my growing panel has problems with showing the right year... It is because of new years I guess. The year should be 2010 but instead it keeps on changing the year. Even if I wait a few hours it still keeps on scrolling from 2010 to 2019... or my phone just crashes when I try to change the date. Does anyone know how to fix this??
It would be much appreciated!
Click to expand...
Click to collapse
Anything news about it?
FerdinandJ said:
Anything news about it?
Click to expand...
Click to collapse
I installt Growing Panel from here http://forum.xda-developers.com/showthread.php?t=606565
and I have no Problem
Do you use it on custom rom?
I have the Unoff X1.5 on my x1.
I got this problem too, removed growing panel from favorites cause everything crashes when I use it. Xpanel works great though
Ok.
I have take the CAB from SE-Homepage and copy FlashPanel folder in ProgramFiles and it runs.
I got the same problem in my cooked rom(Christian's rom). But i'm still using the growing panel from the leaked R3AA beta. Maybe it has to do with that and the new version from the x2 rom have fixed this issue
To bad you allso have this problem, but least it is nice to see that i'm not the only one.
I tried to fix the bug by downloading the official growing panel from se.com, and the time problem was fixed, but certain indicators didn't work. The plants that show battery strength and signal strength don't work anymore. I think this is because it is X2 software. But now i'm wondering if the growing panel that was ripped off the X2 by gtrab will have the same problem, or that it is somehow modified for the X1. Cause I still use the original ROM.
Has anybody tried the growing panel from gtrab's cab post? If you did, can you tell me if it works on the original ROM?
Or does someone know how to fix the indicators?
I know I ask a lot, but I think this will be helpfull to more people than just me
Thanks in advance!
So weird! I had to do a couple of softresets cause of some other problems (dropped my phone down the stairs ) and I thought I'd give the growing panel another shot. And now everything works fine... So I don't know if it was the soft reset or the dropping it down the stairs but growing panel works fine now
SO: GROWING PANEL FROM SE WEBSITE WORKS!
The year on mine changes too. Not sure why.
Install X2_Flash_cab fromthis post :
http://forum.xda-developers.com/showthread.php?p=4640139
and install GrowingPanel from SE-Homepage.
It works.
It definitely does not work that way. I installed the growing panel from se homepage and it crashes when I open a programm or when I whant to bring up the panel manager again. Any other solutions?
Me three with time bug
I second the call for (another) solution to the time bug ... Im leery of installing X2 software on the X1, having tried with no success with other panels (eg YouTube, eWallet). Would it make any difference that I have other flash software installed? (i.e. Adobe Flashlite, Dvha79 AdobeFlash 3.1 plugin, Skunkworks FlashVideoBundle). Any help would be much appreciated. I suppose the Growing Panel is still useable even with the cycling date (year) but it is rather distracting...
Growing panel is removed from x1 section in sonyericsson website! When I install it from x2 section the shortcuts dont work! Does anyone have working growing panel?
Anyone has a working growing panel please?
I know temporary (and it seems that there won't be another ) fix! Everytime you choose growing panel you should change year to 2000 (or another < 2010, but last digit will stuck so it better be 2000) and then change back to 2010.
Thanks for the temp fix Artyom K - obviously not perfect but its far better than nothing! At least the panel is useable now. It has always been a pretty rather than functional panel so having the cycling numbers really defeated the whole purpose of the bloody thing.
Hi,
I do not have the access to post in that forum, so I want to just do a check here, does anyone have this similar problem.
ROM : http://forum.xda-developers.com/showthread.php?t=1945441
Problem: Trackpad no longer works in latest v3.0
V3.0 is all and good, the OS I have been waiting for my desire (for 3 years I dare say) However, the track pad is not working. Anyone have this similar problem or is there something I don't know about that I should be doing.
Thanks!
Hi anybody with the above mentioned rom care to chime in? The ROM is great FYI I have been using it for months. Been thinking about getting another HTC desire to flash it to this rom for my mom.
I don't usually use the track pad, but just tested and it seems ok
Sent from my HTC Desire using Tapatalk 2
frosty68 said:
I don't usually use the track pad, but just tested and it seems ok
Sent from my HTC Desire using Tapatalk 2
Click to expand...
Click to collapse
ah ok thanks, no wonder nobody was complaining in the forum thread... now i'm at a lost what to do. you flashed version 3.0 right? i haven't had this issue until 3.0
whimsywhimsy said:
ah ok thanks, no wonder nobody was complaining in the forum thread... now i'm at a lost what to do. you flashed version 3.0 right? i haven't had this issue until 3.0
Click to expand...
Click to collapse
I just verified this and trackpad is working fine here. Am on v3.0 as well. Did you do a full wipe before flashing?
led notification not work in desire on miui 4.1
whimsywhimsy said:
Hi,
I do not have the access to post in that forum, so I want to just do a check here, does anyone have this similar problem.
ROM : http://forum.xda-developers.com/showthread.php?t=1945441
Problem: Trackpad no longer works in latest v3.0
V3.0 is all and good, the OS I have been waiting for my desire (for 3 years I dare say) However, the track pad is not working. Anyone have this similar problem or is there something I don't know about that I should be doing.
Thanks!
Click to expand...
Click to collapse
i have benn using this rom for about three weeks.i don't have this problem or u reflash the rom.
vijendrahs have new work for htc desire: http://forum.xda-developers.com/showthread.php?t=2070704
dvsk69 said:
I just verified this and trackpad is working fine here. Am on v3.0 as well. Did you do a full wipe before flashing?
Click to expand...
Click to collapse
Sorry was busy for a few days, forgot about this thread, yeah I always do full wipe, not sure what I did but unchecking custom actions and then reboot... suddenly the track pad works again. I tried to recreate the problem by checking the custom actions, couldn't reproduce it... maybe it's just my track pad being dirty after 3 years? dunno. Anyway it works again, thanks for taking time to notify me.
Also... the link to the new work... I think I cannot test alpha builds... I really need my phone. but I will donate again if I move to new version haha, his work is great!
p/s anyone kind enough to explain what is the main difference at least between this new work and existing one? I'm kind of a noob and the last time I tried to read a cyanogenmod nightly changelog I almost fainted. Incremental builds from VJ I can understand, the rest... are totally alien to me, even finding the CM changelog was a challenge!
Just FYI I decided to try out the install a2sd from terminal with the Y Y Y command, and then when I tried to revert it back to the Y N Y setting, all my settings/sms/data was gone. So caveat emptor... or maybe you guys already know this, I for one did not.
Anyway now it's my HOME button that has lost functionality, the trackpad is ok... bummer... I didn't know how much I used it until it was gone. Even the settings under System > Hardware keys > Enable Custom Actions did now show a Home Key button (just has a Home key (long press) option)
er... help? I have restarted a few times... doggone it. I want my home button back!
whimsywhimsy said:
Just FYI I decided to try out the install a2sd from terminal with the Y Y Y command, and then when I tried to revert it back to the Y N Y setting, all my settings/sms/data was gone. So caveat emptor... or maybe you guys already know this, I for one did not.
Anyway now it's my HOME button that has lost functionality, the trackpad is ok... bummer... I didn't know how much I used it until it was gone. Even the settings under System > Hardware keys > Enable Custom Actions did now show a Home Key button (just has a Home key (long press) option)
er... help? I have restarted a few times... doggone it. I want my home button back!
Click to expand...
Click to collapse
I reflashed the ROM everything works now, I guess I was lucky never hard this experience before. I guess next time I should have a nandroid back up.
For anyone that just want an idea of what's the difference VJ has posted it himself. Please find notes below ty.
For actual differences between 4.1.2 and 4.2.1 google yourself.
But the improvements from my CM10 v3.0 to CM10.1 v4.2.1 is that:
1. The games which was not able to play in either any of the Jelly Bean version is playing now and better than GB ROM's.
2. Notification lights works
3. FM Works
4. Much Smoother
5. Video play back is very good (No more flickering)
6. Improved HWA
and find out yourself....
What's not working yet?
Same as Evervolv 4.2.1 (We fixed Bluetooth, Notification lights before them)
for me trackpad works fine
I dont see a lot of posts about this. But, there is a very annoying bug after the update; where if I press the Home Button to wake the screen, it will sometimes launch the task manager about a second later. I've seen sporadic posts about this for Tmobile as well as Sprint for JB 4.1.2 update; but nobody seems to have a solution.
I guess it's possible that some people dont think it's annoying enough to post; or, it's a possiblility it only affects people who have the factory rooted update installed.
I'm hoping someone smarter than me has already figured out a way to circumvent this very annoying behavior. What makes it really bad is that it only sometimes happens.
PS: The only carrier that doesn't seem to have this issue after the 4.1.2 update is ATT. My guess is they caught this bug before pushing it to all their customers.
mkanet said:
I dont see a lot of posts about this. But, there is a very annoying bug after the update; where if I press the Home Button to wake the screen, it will sometimes launch the task manager about a second later. I've seen sporadic posts about this for Tmobile as well as Sprint for JB 4.1.2 update; but nobody seems to have a solution.
I guess it's possible that some people dont think it's annoying enough to post; or, it's a possiblility it only affects people who have the factory rooted update installed.
I'm hoping someone smarter than me has already figured out a way to circumvent this very annoying behavior. What makes it really bad is that it only sometimes happens.
PS: The only carrier that doesn't seem to have this issue after the 4.1.2 update is ATT. My guess is they caught this bug before pushing it to all their customers.
Click to expand...
Click to collapse
I'm going to bet that is you disable your lockscreen you'll see this behavior just about every time. I'm fairly certain I tracked down at least one way to circumvent this behavior - check out this post for some info on it. The take home - my approach requires a wee bit of smali hacking, and everything that utilizing such a solution entails...
Dwitherell, thank you so much for responding. I was even considering on reverting back to 4.1.1 because of this. I don't use any kind password or pattern lock.
Forgive my ignorance, but the post you pointed me to locks like its on a Jedi ROM. I don't even see any specific references to this issue. What is this fix for specifically? If it is for sure going to restore normal behavior, i guess i could try to do this hack.
If this issue is as wide spread as i think it is, is there any chance you could make a tiny root app that fixes the problem or some way of automating a fix for not so technical people? How wide spread is this issue? Thanks a million for your help.
dwitherell said:
I'm going to bet that is you disable your lockscreen you'll see this behavior just about every time. I'm fairly certain I tracked down at least one way to circumvent this behavior - check out this post for some info on it. The take home - my approach requires a wee bit of smali hacking, and everything that utilizing such a solution entails...
Click to expand...
Click to collapse
My annoying fix...
I have been plagued by this since the update as well. I have tried factory resets and uninstall programs one by one. Nothing worked. Today I decided to try removing my lock screen pin, just used the swipe to unlock. That did not work. Then it came to me...
I set back up my pin to unlock, and switched the setting "Lock automatically" to Immediately instead of having a delay that I love. That "worked" as in it no longer goes to recent apps. But now I have to chose to have a pin to unlock it every time my screen turns off or remove security or deal with the recent apps issue. Any way you choose it's an extra annoying step to unlock.
I'd like to hear if anyone else has found any other solution.
Edit.... I have tried every lock option and as long as set to lock immediately, it will eliminate the problem. And the same with setting any delay, with any lock option it will result in the recent apps.
I forgot to mention that lock screen prevents this bug from happenening. I'm guessing that's why not everyone has complained about the issue.. and why the bug somehow sneaked passed beta testing of 4.1.2. I would think this changed behavior was a new "feature" as horrible as it is, but it looks like it dad unintentional since its not consistent behavior.
I'm hoping that a kind android developer who also can't stand this problem, Kay offer a small script or app for rooted user to patch this problem.
mrtolles said:
I have been plagued by this since the update as well. I have tried factory resets and uninstall programs one by one. Nothing worked. Today I decided to try removing my lock screen pin, just used the swipe to unlock. That did not work. Then it came to me...
I set back up my pin to unlock, and switched the setting "Lock automatically" to Immediately instead of having a delay that I love. That "worked" as in it no longer goes to recent apps. But now I have to chose to have a pin to unlock it every time my screen turns off or remove security or deal with the recent apps issue. Any way you choose it's an extra annoying step to unlock.
I'd like to hear if anyone else has found any other solution.
Edit.... I have tried every lock option and as long as set to lock immediately, it will eliminate the problem. And the same with setting any delay, with any lock option it will result in the recent apps.
Click to expand...
Click to collapse
mkanet said:
Dwitherell, thank you so much for responding. I was even considering on reverting back to 4.1.1 because of this. I don't use any kind password or pattern lock.
Forgive my ignorance, but the post you pointed me to locks like its on a Jedi ROM. I don't even see any specific references to this issue. What is this fix for specifically? If it is for sure going to restore normal behavior, i guess i could try to do this hack.
If this issue is as wide spread as i think it is, is there any chance you could make a tiny root app that fixes the problem or some way of automating a fix for not so technical people? How wide spread is this issue? Thanks a million for your help.
Click to expand...
Click to collapse
It was posted in a Jedi thread, but only because that is where I noticed it was mentioned. The context outside that single post was someone stating the same observation as you, my responding saying that I was also annoyed by it, with a later edit saying I may have come up with a workaround for it, and their response of "tell me more". As far as automating a fix or creating an app or the like - that is well beyond my paygrade unfortunately. What are you running? If you are interested you could PM me - all I need is your android.policy.jar (or to know what you are currently running) and I can try to get a fix together for you given some other conditions (i.e. have a custom recovery installed so you can flash things). It seems to have fixed it on my end, but I would be very interested in getting some others to test
You did it! Your fix works perfectly! The bug is gone! ...like the bug was never there. My understanding is the fix prevents the phone from stupidly trying to launch the task manager when the screen wakes by the home button. I also donated for you time and effort. Thanks a million.
dwitherell said:
It was posted in a Jedi thread, but only because that is where I noticed it was mentioned. The context outside that single post was someone stating the same observation as you, my responding saying that I was also annoyed by it, with a later edit saying I may have come up with a workaround for it, and their response of "tell me more". As far as automating a fix or creating an app or the like - that is well beyond my paygrade unfortunately. What are you running? If you are interested you could PM me - all I need is your android.policy.jar (or to know what you are currently running) and I can try to get a fix together for you given some other conditions (i.e. have a custom recovery installed so you can flash things). It seems to have fixed it on my end, but I would be very interested in getting some others to test
Click to expand...
Click to collapse
No, thank you for making me learn how to put an odexed mod together and testing it for me!
So this fix will work for anyone running a stock odexed version of 4.1.2 UVBMB4 - you just need to be rooted, and having a custom recovery would be nice so you could flash it but you could also just copy the files over. That being said - would this be worthwhile to post?
I wish i had know i could just copy the files over.. that's actually less convoluted process than depending on a script. I thought the reason you made a patch via flashing is because the system files were locked/open by the system. Anyway, i am extremely thankful for this'll as there is no other way to fix the bug without adding extra steps to wake the screen.
You should definitely share both odexed and deodexed patches with others. I personally don't know how i could tollerate that bug for much longer. I'm sure there are others who don't use the lock screen. Plus, this would give a chance for others to appreciate your work by dontating for your time and effort.
mkanet said:
I wish i had know i could just copy the files over.. that's actually less convoluted process than depending on a script. I thought the reason you made a patch via flashing is because the system files were locked/open by the system. Anyway, i am extremely thankful for this'll as there is no other way to fix the bug without adding extra steps to wake the screen.
You should definitely share both odexed and deodexed patches with others. I personally don't know how i could tollerate that bug for much longer. I'm sure there are others who don't use the lock screen. Plus, this would give a chance for others to appreciate your work by dontating for your time and effort.
Click to expand...
Click to collapse
The flashable zip is just one method to get the files where they need to go. Literally all it does is overwrite the 2 files in /system/framework by moving the 2 files over from the zip - but there are definitely other ways to do such things. Some are more comfortable with this route, others are more comfortable w/ getting /system to be rw and move the files manually.
I'll likely post this at some point in the next few days
I don't mean to revive a dead thread or anything, but this bug has been driving me CRAZY & the smali hacking worked perfectly for me, thank you!!!
FYI, I'm willing to help people out with this as well. If anyone wants this done but doesn't wanna mess with the java stuff, PM me & send me your android.policy.jar and I'll hack it for you
kabuk1 said:
I don't mean to revive a dead thread or anything, but this bug has been driving me CRAZY & the smali hacking worked perfectly for me, thank you!!!
FYI, I'm willing to help people out with this as well. If anyone wants this done but doesn't wanna mess with the java stuff, PM me & send me your android.policy.jar and I'll hack it for you
Click to expand...
Click to collapse
Glad to hear
Is it possible that my phone isn't affected? If its a 4.1.2 bug, it should be in all phones with same version right?
This is not happening to my phone. Whether I have lock screen activated or not. I'm rooted but running stock ROM and I have Nova launcher installed if thats even important.
It's not all notes.
Sent from my SGH-T889 using xda premium
kabuk1 said:
I don't mean to revive a dead thread or anything, but this bug has been driving me CRAZY & the smali hacking worked perfectly for me, thank you!!!
FYI, I'm willing to help people out with this as well. If anyone wants this done but doesn't wanna mess with the java stuff, PM me & send me your android.policy.jar and I'll hack it for you
Click to expand...
Click to collapse
is this offer still good? i'm was experiencing the same problem and it was so annoying that the only solution i found was to revert back to 4.1.1. I'm currently running t889uvall4.
also, my phone is not rooted. will the fix dwitherell came up w/ work? or do i really have to root my phone?
wesblogger said:
is this offer still good? i'm was experiencing the same problem and it was so annoying that the only solution i found was to revert back to 4.1.1. I'm currently running t889uvall4.
also, my phone is not rooted. will the fix dwitherell came up w/ work? or do i really have to root my phone?
Click to expand...
Click to collapse
Yes you'll need to be rooted unfortunately - sorry
wesblogger said:
is this offer still good? i'm was experiencing the same problem and it was so annoying that the only solution i found was to revert back to 4.1.1. I'm currently running t889uvall4.
also, my phone is not rooted. will the fix dwitherell came up w/ work? or do i really have to root my phone?
Click to expand...
Click to collapse
Absolutely. just PM me. Yeah, you have to be rooted but that's easy to do & worth it for this hack & all the other things you can do once you're rooted.
kabuk1 said:
...Yeah, you have to be rooted but that's easy to do & worth it for this hack & all the other things you can do once you're rooted.
Click to expand...
Click to collapse
^^^ THIS - a thousand times over
Hey guys, I'm kinda new to this modification world, started when I received my Zenfone 2 out of necessity since ZenUI is very poluted and ended up enjoying it
So, right now I'm using SuperZen (super basic) just to get rid of the endless bloatware that comes with the phone... my question is: what is the best overall rom right now for someone who is starting and want something very clean?
Other thing, the double tap feature still working in these others roms or just in stock? Cant live without it, I came from LG G2 and I cant stand at clicking the power buttom anymore... I know that sounds idiotic but is really cool to have this feature...
Hi, i recently installed the CM13 mod, the one released on 23 July 2016, and i can't seem to get past the initial account setup. Every time i press the next or back buttons on the screen the notification bar scrolls down. I can't seem to get past it, and it doesn't seem to have happened to many others. I've looked at other forums and am yet to find a definitive answer. They either gave up or switched ROMs. I can't do either due to lack of resources and would really appreciate your help. Also, i am very new to this, which makes matters all the more difficult
Thank you
Hi , i'm having exactly the same problem but on a frech install of cm13 on a samsung i9100.
Can't find any info about this problem, did you find a way to bypass initial setup?
t.R.j said:
Hi, i recently installed the CM13 mod, the one released on 23 July 2016, and i can't seem to get past the initial account setup. Every time i press the next or back buttons on the screen the notification bar scrolls down. I can't seem to get past it, and it doesn't seem to have happened to many others. I've looked at other forums and am yet to find a definitive answer. They either gave up or switched ROMs. I can't do either due to lack of resources and would really appreciate your help. Also, i am very new to this, which makes matters all the more difficult
Thank you
Click to expand...
Click to collapse
First I would try a factory reset. If that doesn't work, re-download the zip file and reflash. Could a bad download
Sent from my ASUS_Z00A using Tapatalk