Related
Hi I am on Nero v5 and I wanted to add the AOSP calendar I got from the Gingerclone r2 rom. I installed via root explorer and everything is fine, but there is this grey bar on the top that I can't get rid of. I tried searching and installed different apks, but none of them fixed this problem.
To my knowledge I do not think we have a fix... I had the same issues a long time ago when I used AOSP. Have you tried d/loading an AOSP rom and moving the .apks from that rom to system/app?
I have not tried that. It may work.
Yeah and I still had the same problem
I read A POST a LONG time ago where someone said they had it working.... I believe I even sent them a PM, but it has been deleted. I know someone claimed to have done it, so maybe with luck searching.... please pm me if you find the answer.
OP, you may want to keep an eye out here:
http://devsforandroid.com/ip.board/...osp-clone1001202011/page__gopid__484#entry484
Getting rid of white bar In AOSP calendar
"The framework-res.apk hack is just replacing timepicker_input_selected.9.png file with one that's totally transparent"
from: http://forum.xda-developers.com/showthread.php?t=774914
I did this when placing AOSP calendar on my vibrant. Worked great, seems to have no other adverse effects. (this is on 2.1 but it should be the same)
That being said though, after reading further in the thread, it seems implicated that Eugene's later calendars from his roms do not call for that .png , so you may pull a calendar out of one of his later AOSP ROMS and see if that works before messing with your framework, wich I found to be difficult on the vibrant, (although I did it mostly on the phone which was part of my problem, if I just waited til i was in front of a computer it would have been easier)
EDIT : just realized you did get your calendar from Eugene, so you may want to ask over there how he fixed it or use above solution.
Hi all,
I've just registered to the forum but I've been visiting it for quite some time. I'm afraid my problem is being discussed in a thread but so far I was not able to find it.
I'm currently running CM7 J019 K007 with no reboots. Everything seems to work perfectly except for 2 things:
1. The camera is not working (not even in VGA). When I start the camera it appears to work but when I try to take a picture the image hangs and nothing happens unless I press the home button. The same applies to video.
2. I don't see the starting animation, is just a static image. And when I put a theme, even the default ones, there is no background, just a black screen.
I've tried several things to solve this and I don't know what I'm doing wrong. I've done all the standard steps:
1. Flash bb
2. Wipe everything (partition, Dalvik, etc)
3. Flash ROM
4. Flash apps
5. Reboot
But still those 2 issues continue to happen. I've also tried with J017 and J018. Got them running without an issue except those 2.
Can anyone help me get this fixed?
Btw, I've also tried this:
http://forum.xda-developers.com/showthread.php?t=949262
but still no solution.
Thanks for the help and sorry if it was posted somewhere else.
It is known that the camera might not be working in 2.3 roms.
Thanks aR_ChRiS,
I thought that too but in the threat that discusses CM7 it says the following:
-camera (almost done - works only on low res <=VGA)
And my camara doesn't work even at those resolutions.
Regarding the other issue, I think there must be a corrupt app package in the app zip file but the strange things are that I've downloaded it several times already and that everyone else doesn't seem to have this issue.
reymomo said:
Thanks aR_ChRiS,
I thought that too but in the threat that discusses CM7 it says the following:
-camera (almost done - works only on low res <=VGA)
And my camara doesn't work even at those resolutions.
Regarding the other issue, I think there must be a corrupt app package in the app zip file but the strange things are that I've downloaded it several times already and that everyone else doesn't seem to have this issue.
Click to expand...
Click to collapse
As J told in the thread. This release is only WLOD hunting. These have dissapeared so the coming days he will work on bug fixes and dalvik craches. He made almost a super stable CM7. Actually you can call it with this release stable but not fully functional.
On my phone my camera only work on 3mgp and video only works on low30mm.
Sent from my X10i using XDA Premium App
As for animations they are off by default go to settings/display/animations then choose. The daufault boot screen is supposed to be a static image, that's the way its meant to be. You can change it if you have root explorer if you put this http://db.tt/X8BJiAb in either data/local/temp or or go to system/media and cut the file bootanimation.zip and paste to your SD card and then move the downloaded one to system/media. Don't unzip the file in either way. I think J said he was hoping to get the camera working soon but can only be done after Sony releases their 2.3. Hopefully this info shall help you out
Sent from my X10 using XDA Premium App
Ok then, my bad with the animations since I thought the opening screen at boot was animated as it was in 6.something.
In any case, the mayor problem was the camera. I mean, I'm ok with not having 8Mb pictures, or only with 3Mb. But I'm not able to take pictures at all.
Anyway, I decided to go back to FreeX10 until something else comes along.
Thank you all for the help though
I have only tested this on the CM9 nightlies, so if you decide to try it on anything else, make a backup beforehand and report if it works for you.
Do you want Google Now on your HP Touchpad? Of course you do. I have been following this thread for a while waiting to get Google Now on my ICS phone.
http://forum.xda-developers.com/showthread.php?t=1747224
XDA member cajunflavoredbob has been keeping a post updated with the latest flashable zips. So keep checking back for the latest one here:
http://forum.xda-developers.com/showpost.php?p=29756226&postcount=2856
I have used these files on my phone and got Google Now working for me. I decided to try the same thing on my TouchPad and it is still a bit buggy but worked pretty well. Voice search and talk back all worked (still buggy though). Just flash in CWR. I dont know if there is any easy way of removing it. So make a backup of your ROM just in case you want to revert back.
I started from a fresh flash of CM9's most recent nightly and then flashed Google Now v6.zip. I was able to get Now working a few times for searches but since have received the "double take" bug that does not automatically set a time reminder etc. After a couple attempts, pressing the MIC button shows an "initializing" screen and does not function.
I've read through his post several times over looking for a fix via permissions, disabling voice actions, etc, but have not been able to get it working 100%. What is your status with it on your TP?
suasponte 375 said:
I started from a fresh flash of CM9's most recent nightly and then flashed Google Now v6.zip. I was able to get Now working a few times for searches but since have received the "double take" bug that does not automatically set a time reminder etc. After a couple attempts, pressing the MIC button shows an "initializing" screen and does not function.
I've read through his post several times over looking for a fix via permissions, disabling voice actions, etc, but have not been able to get it working 100%. What is your status with it on your TP?
Click to expand...
Click to collapse
I think we're on the same page. When it works, it works well. But it still has small bugs. Pressing on the mic in the search bar seems to work better. But at least every feature is there now. A step closer.
Yeah, I'll keep my eye on that thread. I switched around a couple of the updated velvet.apks since there were a few floating around, stated as working, to no avail but I will continue to test fixes. Any bets on whether his Google Now fix or a stable CM10 for the TP is released first?
OP updated with link to latest files.
I'm using reeko's zip, it fails on first try about half the time but when i retry it works pretty much always, if not i retry again lol
I did install the google voice search from app store after flashing the zip. I set the mic to go to this voice search, and pressing the word google brings up google now. So I have one that always works, and one that kind of almost always works.
I'm using the online only version of the zip, I don't know if the offline would need to initialize to google server or if it would work without failing
I havent even tried the offline version. But it sounds like they have similar issues. When you say you retry, do you hit the mic icon or the actual word "Retry"?
either one, or both
i just tested it, it works with doing either, it really is hit or miss it seems. around 15-20% success rate sometimes. I mean I hit retry/mic (depending on how bored i am) and I can do this around 10 times before getting it to work once. Then other times I can get it to work 3-4 times in a row before failing again
edit: from what I can tell (or what it looks like to me) hitting retry, retries in the app. hitting mic relaunches app? i say this since i see it kind of jump, like the entire app relaunched quickly. So my take is if this launch didnt work, i hit mic to relaunch it and hope this time is a bit better
eyeb said:
either one, or both
i just tested it, it works with doing either, it really is hit or miss it seems. around 15-20% success rate sometimes. I mean I hit retry/mic (depending on how bored i am) and I can do this around 10 times before getting it to work once. Then other times I can get it to work 3-4 times in a row before failing again
Click to expand...
Click to collapse
I kinda have a feeling one of the older files worked better.
If you get bored, try this file out. This was the first one I came across but havent gotten around to flashing it back to see if it was better.
https://www.box.com/s/78f4efb985d94487d5d5
I am also hitting about 10%. Whether or not I hit mic or reset. I play with the settings, changing language and what not and it seems to reset it. But still hit and miss...
Same. Im running CM9 nightly 8/07, tested flashing every G Voice rom and the same error occurred with each one. I came across a post saying G Now only worked with a specific ICS rom, but I cannot find that particular post anymore nor a post on the main thread with a CM9 TP confirming G Now is working.
I'm also having problems getting G Now to work properly on the HP Touchpad with the latest nightly build.
Only thing that is buggy which today for me stopped working altogether is the voice search.
Anyone figure out how to fix this yet?
I'm not a developer but shouldn't it be possible to get G Now working for CM9? Since it is running ICS.
It would be awesome to get Voice working.
Here goes. I have the 4.1.1 Omega v32-XXDLJ5 ROM with Siyahkernel v1.7rc2 on my I9300.
Now the problem is, the ROM was working perfectly without any hitches, but today when I tried using Google Voice app, the voice failed to take my input and kept asking me to tap the microphone icon onscreen. I can see that it is registering the voice (with the visual representation surrounding the microphone icon), but there is no feedback. Upon checking further I found that the same issue is with Samsung's Assistant as well. It is not providing any feedback.
Unfortunately that's not the end. I also found that the dictation in messaging etc. of Google voice isn't working either. So, basically, they all are listening to my voice but not providing any reply/feedback.
Same issue had happened to me before 10 days. At that time I had felt that I might have tweaked with some setting somewhere which resulted in this issue (did a nandroid restore to resolve it). But this time around, i haven't done anything which would have caused this issue.
Can anyone help me to find the cause of this issue, and if anyone knows what/where the fault is, your help in resolving this issue will be appreciated.
I know I can reflash the rom/restore the nandroid backup, but it also means having to re-install everything/some from scratch, which is a pain. And also, those don't identify the source of the problem. And this being the 2nd time, it might very well be repeated a 3rd or more number of times.
Did you try fix permissions in CWM.
I have the CWM 3.60, but i get a notice that this ver of CWM should be used with CF-CWM v1.1 or newer, so, various options have been diabled. Maybe that's why I don't have the fix permissions option. Any idea about this?
NB: Found the option in CMR and it fixed the issue right up. Thnx a lot buddy
Sorry if this thread already exists.
You have no idea how happy I am this ROM exists!! But I cannot get SMS working. I get FC's on every SMS app I try including Hangouts. Anybody else getting this and/or have a remedy? Thanks
I was about to post the same error here, I have an Amaze with Videotron, S-Off, Super CID, HBOOT-1.93.2222 (JuopunutBear), TWRP as a recovery.
I tried everything, I tried different Gapps, I also tried without installing Gapps, I tried sms apps from the Play Store and Hangouts too. The only thing I haven't tried is formatting my internal SD card. (it was a clean install, all formatted and cache cleared). I also tried switching to ART but I had the same problems.
Everytime I try to just open the sms apps, the app crashes. I managed to see the error once and it was something about SQL but it might be a misinterpretation from my part.
Calls, 4G and WiFi were all working perfectly too.
After some research on Google, I tried installing busybox, xposed framework and uninstalling Voice+, but nothing works. The basic messaging app just closes without any kind of message and other apps show that it stopped working.
(I tried the Evervolv rom 4.4 and SMS were working on that one, maybe it's a setting with my network type as I am on Videotron in Canada and it is using AWS, maybe a setting under *#*#4636*#*# ??)
I want to contribute and sen some log of that error, how can I do that? I am familiar with roms, kernels, etc but not that much with logs... I tried many roms before and never got that specific problem...
Thanks to anyone who can help with this issue!
It's not just you SMS simply doesn't work on this rom and I was surprised to see that no one else pointed this out in the original thread. The default Messaging app closes immediately when you try and open it. Other SMS apps also crash either immediately upon opening them, or when you try to send a message (hangouts & SMS Pro for example). This is the only thing keeping me from using this amazing rom as my DD.
I have the same exact problem with SMS- will try the evervolv 4.4 though was really looking forward to CM11
Edit: also didnt have any other problems with the rom except for the black boxes and the camera
Let's hope there is a way to fix it!
I would post the question in the official thread but I do not have enough posts to do so unfortunately
Heck I couldn't even try SMS due to the black box issue, that's why I didn't mention it in the original thread.
For those with the black box issue--are you using the correct gapps?
In olden days there were some issues with some google things not working, and people uninstalling the ones that came in gapps and downloading them fresh from the play store.
Have you gone into recovery and fixed permissions?
Again, in days of yore, this might straighten some things out.
Is it possible that black-boxing has something to do with CPU frequency, and is it possible to tweak up the speed through developer options and lose the boxes?
I haven't tried this rom yet, as I'm currently sticking with the stable(r) cm10.
Good luck.
anybody get the SMS working on this ROM so far?
pbergonzi said:
For those with the black box issue--are you using the correct gapps?
In olden days there were some issues with some google things not working, and people uninstalling the ones that came in gapps and downloading them fresh from the play store.
Have you gone into recovery and fixed permissions?
Again, in days of yore, this might straighten some things out.
Is it possible that black-boxing has something to do with CPU frequency, and is it possible to tweak up the speed through developer options and lose the boxes?
I haven't tried this rom yet, as I'm currently sticking with the stable(r) cm10.
Good luck.
Click to expand...
Click to collapse
The black box issue has nothing to do with GPU or CPU speeds. There are discussions on the dev threads. The issue affects other legacy devices on various KK based source builds, not just Amaze and CM. The consensus is this seems to be related to the default browser which has changed in KK. This would also explain why it effects other gapps too.
MS92 said:
anybody get the SMS working on this ROM so far?
Click to expand...
Click to collapse
Not that I'm aware of.
Media Issues
The ROM is pretty good for the most part.
I just have this problem where Play Music gives this error, "Cannot play the music track you requested"
I clear my media storage and try to rescan my SD card but none of the apps work. They all crash.
Is there anyway to fix this?
ranwal said:
The ROM is pretty good for the most part.
I just have this problem where Play Music gives this error, "Cannot play the music track you requested"
I clear my media storage and try to rescan my SD card but none of the apps work. They all crash.
Is there anyway to fix this?
Click to expand...
Click to collapse
Maybe app settings for the app and Erase App Data?
can i get a link for the updated adreno drivers? thanks!
865DETH said:
can i get a link for the updated adreno drivers? thanks!
Click to expand...
Click to collapse
Yes you can its on last three pages of orignal thread you also have to sign up for that
Sent from my HTC_Amaze_4G using Tapatalk
as the OP says and i quote that only non working things are
1. camera exposure
2. tethering
but as the thread goes ahead we read more prolems/bugs
May i ask what is the current status for bugs/not working and other issues and what has been fixed and any other stuff we should flash over the ROM like driver, may it be upoaded to the OP for ease as its reall hard to search for those things on mobile app. thank you and good luck.
Anyone else have issue disabling their microphone while in a call? I tried with both the speaker phone and regular handset mode, the "no mic" icon enables but my caller can still hear me. The Hold button seems to work fine though.
FYI, it took a while for the battery to figure itself out. I wiped the battery stats before flashing everything and the first few days I got a lot of jumping battery levels. I let it charge all the way down as much as I could then rebooted and did a full charge and rebooted again and then full charge again. That seemed to reset the battery level to the correct state.
I also , enabled Device/GPS only for the location detection other wise the google services at 50% or more battery.
I'm running the 2014-02-16 build, with the updated video drivers.
Camera is not working
I have also installed this pacman rom 4.4.2. all is well instead of camera.
Any updates for the camera isssue??
Shahxz said:
I have also installed this pacman rom 4.4.2. all is well instead of camera.
Click to expand...
Click to collapse
Since PAC uses the CM device tree for its source any issues with CM will also be evident in PAC. Until the CM devs are able to resolve the camera exposure issue it will exist in both ROMs.
Librastar said:
Any updates for the camera isssue??
Click to expand...
Click to collapse
Think about your question for a minute. Have you seen any recent posts in the CM dev thread indicating an update which solves this issue? If you had just taken a moment to look at the dev thread instead of posting this you would have answered your own question. It's not like the CM-11 thread is incredibly long, it's only 28 pages total. This post is just laziness on your part and an unnecessary waste of bandwidth.
is there any alternate app in the market, i tried couple of apps but nothing useful
@Odysseus1962
If I were to compile AOSP, which variant would you suggest for me to build?
Sent from my SAMSUNG-SGH-I747 using Tapatalk