Hello,
After upgrading my Qtek A9100 G4 with TNT 1933 Professional + HTC Home, I can't change themes anymore. when I choose a theme, averything goes as if the theme will be applied but nothing happens. I'm stuck with Windows Default theme.
I've tried a lot of different TSK files but none seems to work. I can't get rid of Windows Default theme.
Any cure for this?
I had that problem with a ROM that I cooked myself before. About the only solution is to reflash the ROM again and if it still does it then it's probably time to try a different ROM. When I had that problem it wasn't the only thing that went wrong, I also had problems with ringtones not sticking and reverting back to the default one along with a few other things, so the theme not changing may just be the tip of the iceberg.
Flash your carrier's rom 1st, so you get a clean base then flash back.
I always flash the cingular one 1st then the new wm6 and i never have these kinda issues.
Now working
That's it. Everything is working now. My steps:
1. cleaned extended rom
2. installed Wizard Love
3. reinstalled TNT pro + home
And now everything works and I can get rid of the ugly windows default theme.
Diamened said:
That's it. Everything is working now. My steps:
1. cleaned extended rom
2. installed Wizard Love
3. reinstalled TNT pro + home
And now everything works and I can get rid of the ugly windows default theme.
Click to expand...
Click to collapse
Lesson learned!! Install official ROM before flashing custom ROM!!!
ai6908 said:
Lesson learned!! Install official ROM before flashing custom ROM!!!
Click to expand...
Click to collapse
after being a member of this site since early 05, i've never once flashed back to the provider rom, and i've never had a problem. Two devices, blue angel and the wizard. Don't waste your time doing that, probably just needed to reinstall the rom. It happens, my two cents, peace
My specs: LG P500 Optimus One, rom: cm 10.1.0 RC3, i flashed soft and then gapps for 4.2.1
I flashed new build and i noticed, that notification area is not working properly
I cannot access quick toggles panel by clicking the top right icon.
Also swiping on the bottom bar causes weird bug, if i swipe half the way or stop swiping in between, the toggles are not flipping completely and are not clickable sadly .
Another thing is that first run android setup does not run at all after flashing 4.2.1 rashed's gapps. (on 24.04 nightly it works though)
And cronmod is not working, but i guess it's the 3.0 kernel thing. (is there any way to have something like cronmod with 3.0?)
If any of you can point me where to report bug and had experienced those too, please help me, thank You in advance.
I tried to search some contact form on jenkins, but with no luck :C
Jacek95 said:
My specs: LG P500 Optimus One, rom: cm 10.1.0 RC3, i flashed soft and then gapps for 4.2.1
I flashed new build and i noticed, that notification area is not working properly
I cannot access quick toggles panel by clicking the top right icon.
Also swiping on the bottom bar causes weird bug, if i swipe half the way or stop swiping in between, the toggles are not flipping completely and are not clickable sadly .
Another thing is that first run android setup does not run at all after flashing 4.2.1 rashed's gapps. (on 24.04 nightly it works though)
And cronmod is not working, but i guess it's the 3.0 kernel thing. (is there any way to have something like cronmod with 3.0?)
If any of you can point me where to report bug and had experienced those too, please help me, thank You in advance.
I tried to search some contact form on jenkins, but with no luck :C
Click to expand...
Click to collapse
i'm using the CM10.1.0 RC2 jenkins build too.
i did a clean install, and had no problems with the notification.
though the first run android setup did crash for me too..[flashed the ROM twice]
i guess you should do a clean install!!
Do a clean install. One more thing, gapps are already included in the builds.
No need to flash the gapps
Jacek95 said:
My specs: LG P500 Optimus One, rom: cm 10.1.0 RC3, i flashed soft and then gapps for 4.2.1
I flashed new build and i noticed, that notification area is not working properly
I cannot access quick toggles panel by clicking the top right icon.
Also swiping on the bottom bar causes weird bug, if i swipe half the way or stop swiping in between, the toggles are not flipping completely and are not clickable sadly .
Another thing is that first run android setup does not run at all after flashing 4.2.1 rashed's gapps. (on 24.04 nightly it works though)
And cronmod is not working, but i guess it's the 3.0 kernel thing. (is there any way to have something like cronmod with 3.0?)
If any of you can point me where to report bug and had experienced those too, please help me, thank You in advance.
I tried to search some contact form on jenkins, but with no luck :C
Click to expand...
Click to collapse
Gapps are already included in the ROM. No need to flash them again. If you flash the gapps, you may get those bugs as there isn't enough space for ROM as well as gapps.
try a clean install without flashing gapps.
rhar**** said:
Gapps are already included in the ROM. No need to flash them again. If you flash the gapps, you may get those bugs as there isn't enough space for ROM as well as gapps.
try a clean install without flashing gapps.
Click to expand...
Click to collapse
okay, will try now and report results soon
thanx for your effort
Okay, everything working fine, me flashing gapps over embedded ones in rom was the problem.
Hello.
My problem is that sometimes, when I receive a notification, ambient display turns screen on to show it (as it should do normally), but then, when it is supposed to turn screen off again, it only goes black, but the backlight is still on. It's hard to notice, but I don't want the backlight on, using battery, when I think it's off.
The only way to turn it off is by activating ambient display again (moving the phone, waving in front of proximity sensor, pressing power button), and then it would show my normal lock screen and then turn off, until "something" makes it leave the backlight on again.
Anyone have/had/knows this issue? I've used Mokee ROM, now I'm on RR and it happened on both, I don't remember if it happened in CM. Could it be something app related?
Thanks.
Yeah same happened with cm 12.1 latest nightly too.....just checked it now...
The Answer
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
therealduff1 said:
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
Click to expand...
Click to collapse
That's strange! I guess it may be something like the drivers you said, because just one user said that have the same problem, but I'll have to wait until I have some free time to flash stock and root and flash CM and restore all apps and that again... I hate that part of installing another ROM.
therealduff1 said:
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
Click to expand...
Click to collapse
I flashed stock using fastboot and then RR but the problem persists... Any other ideas??
Secuential said:
I flashed stock using fastboot and then RR but the problem persists... Any other ideas??
Click to expand...
Click to collapse
Ok, I have spent some time thinking about this one for you, as I really want you to get this one fixed!
Although I need abit more information.
1) Does the issue occur on stock rom?
2)Are you sure it is not a problem with the build you are running?
3)What exact steps did you use to flash the rom?
To show that you appreciate my help so far, please click thanks
therealduff1 said:
Ok, I have spent some time thinking about this one for you, as I really want you to get this one fixed!
Although I need abit more information.
1) Does the issue occur on stock rom?
2)Are you sure it is not a problem with the build you are running?
3)What exact steps did you use to flash the rom?
To show that you appreciate my help so far, please click thanks
Click to expand...
Click to collapse
Thanks!
1)I can't tell if it occurs on stock, because on stock I use moto display (which doesn't have this issue).
2) I'm almost sure, because I've used 2 ROMs and both do the same. Maybe I'll have to try with CM nightlies?
3)I followed the guide in "general" section to flash stock using fastboot and android sdk. After that, I booted on stock, then rebooted to bootloader, flashed TWRP, entered to recovery, wiped data and then flashed RR ROM with it's gapps and then flashed moto camera and gallery. After that, wipe dalvik and cache and rebooted to system.
Right , ok. I recommend trying one of the cm12 nightly builds, seeing as they worked on my phone fine in terms of ambient display
therealduff1 said:
Right , ok. I recommend trying one of the cm12 nightly builds, seeing as they worked on my phone fine in terms of ambient display
Click to expand...
Click to collapse
Well, the other user that commented on this post was also using latest CM nightly, so I'm not very positive about it, but I may try it when I have time.
Well , looking at all of the information In this post , I think it is safe to say ambient display is not fully working on many roms :/
I installed a new build of cm12 earlier, and I found that sometimes the backlight will stay on , but other times it is fine.
If you want to work on this together, email me at [email protected] , and then we can look into it abit further ?
I will take a thorough look into the forums to see if others are recieving any problems as well .
therealduff1 said:
Well , looking at all of the information In this post , I think it is safe to say ambient display is not fully working on many roms :/
I installed a new build of cm12 earlier, and I found that sometimes the backlight will stay on , but other times it is fine.
If you want to work on this together, email me at [email protected] , and then we can look into it abit further ?
I will take a thorough look into the forums to see if others are recieving any problems as well .
Click to expand...
Click to collapse
Thanks! I have a lot of work right now, so I can't work with this now, but I'll email you when I have more free time!