Related
Dear Friends.
Here is my release.
Name: PIKI-Build V.01
Features:
+ Kernel Hastarin r8
+ Cyanogenmod 6.1
+ Stock Theme
+ Echo audio Fixed
+ Wireless TETHERING Working (using Wireless Tether application included)
+ 3G SUPERSTABLE, DNS UPDATED AND SPEED IMPROVED (ril wrapper 0.3,opendns,settings changed)
+ 5 mA standby
DIRECT DOWNLOAD
(no wait etc).
link
http://www.tmtecnologic.com/pikibuild/PIKI-Build-v0.1.zip
+ This is an open release.
So you will tell me what would you like that I change..and I'll do it.
remembers
# Do not use AUTO brightness, use manual.
Or if you want to use auto, change values into cyanogenmod setting menu
Enjoy!
tx, i'm downloading
Could you post some screenshots please?
Thank you. Going to give it a go.
Thanks will try it
cd78 said:
Could you post some screenshots please?
Click to expand...
Click to collapse
go to cyanogenmod.com if you want screenshots. it's stock 6.1. does anyone not know what stock cyanogenmod looks like?
Installing right now.
Hope this will work 4 me
robkoehler said:
go to cyanogenmod.com if you want screenshots. it's stock 6.1. does anyone not know what stock cyanogenmod looks like?
Click to expand...
Click to collapse
I know what it looks like but there will be people who dont and i guarantee no screens will mean not as many people download it and try it.
Its nice to see what you are downloading.
I will try this now.
I am agog if data will drop or not
Ganna tell you in the next days
€dit:
OK gonna removing this after testing 30 minutes
2x Backscreen
2x cant install app that i need
ok now waiting for better one
if im gonna change kernel to hastarin 7.7, mobile data gonna still working?
thank you
wifi tether?
gave it a test but it doesnt seem to work just kept giving me a force close error
restarted it and still nothing other than that works great i need a good build w/o sense =]
My experience with this build so far negative. Robotic voice and Black Screen in just 3 min of use. (stock 3.14 WM with stock 2.15 radio) After MDJ's revolution V2.3 with r7.7 this one looks like it need some work on stability. I was checking it because of 5mA promise. Disappointed a bit.
avetny said:
if im gonna change kernel to hastarin 7.7, mobile data gonna still working?
thank you
Click to expand...
Click to collapse
99% yes =)
psvmr said:
My experience with this build so far negative. Robotic voice and Black Screen in just 3 min of use. (stock 3.14 WM with stock 2.15 radio) After MDJ's revolution V2.3 with r7.7 this one looks like it need some work on stability. I was checking it because of 5mA promise. Disappointed a bit.
Click to expand...
Click to collapse
Have you tried to change the stock WM?
Because I had bad experiences with stock rom.
jvillejoe said:
gave it a test but it doesnt seem to work just kept giving me a force close error
restarted it and still nothing other than that works great i need a good build w/o sense =]
Click to expand...
Click to collapse
Try run Superuser first =)
Because that program need root =)
only thing i've ran into so far is not being able to download paid/protected apps from the market
Wow!! So many negative comments lol.
Anyway, download and installed last nite and so far i'm quite impressed with the data. Usually on all builds I've flashed, data is guaranteed to drop after couple of hours of installing, but since yesterday its been cool.
Only problem so far is that when it wakes up from sleep, I can see the screen, but then screen goes blank immediately for few seconds.Have to keep trying to wake it up.
But no thanks, good build.
Works good so far. Thx!
If the screen goes black put it under a bright lightbulb and then turn off auto brightness, how us 3g for real? Anybody? I'm so wanna test this if 3g is stable!
Sent from my HTC Desire using XDA App
psvmr said:
My experience with this build so far negative. Robotic voice and Black Screen in just 3 min of use. (stock 3.14 WM with stock 2.15 radio) After MDJ's revolution V2.3 with r7.7 this one looks like it need some work on stability. I was checking it because of 5mA promise. Disappointed a bit.
Click to expand...
Click to collapse
Listen dont use android with the stock WM.
Download a custom WM ROM most of them are android compatible
YOU'LL HAVE NO ISSUES . I promise
Hi guys, I have an issue with Sat Nav volume. I will try to break it down simply:
Sat Nav [CoPilot and Navigator tested]
Music app [PowerAMP and HTC Music tested]
Audio cable [3.5mm audio jack - plugged into car stereo]
Sound settings all full [set in Quick Settings and also manually set Navigation Volume when Google Navigator is running]
Audio is fine when any music app playing [with or without cable]
Audio is fine when any Sat Nav voice playing [with or without cable]
Audio is fine when any Sat Nav + any Music app both playing (music cuts out and voice becomes audible) [WITHOUT CABLE]
--- Sat Nav voices becomes too low to hear when both Sat Nav and Music playing with cable plugged in ---
This was working perfectly fine on stock HTC (both Froyo and GB) with kernel Buzz OCUV 1.0.6.
I have only seen this issue since flashing Android Revolution HD 5.1.9 > 5.1.10 > 5.1.11 . I have tried different kernels ( Stock ARHD > UnityV2 > UnityV3 ) and also retried Buzz OCUV 1.0.6 but the issue still remains.
Does anybody have any ideas as to what could be the problem?
Anybody have any ideas at all?
Sent from my Desire HD using XDA App
I've always had this issue too, All I have been doing is lower the music volume to half, set Navigation Volume to Full and then increase the car volume instead
According to google support forum, It looks like the issue is caused by GB 2.3.3, 2.3.2 does not have this problem so it seems downgrading is the only fix.
I have the same exact problem unfortunately.
I'm guessing you're using Google Navigation instead of HTC's Locations Premium Navigation?
I'm currently on 2.3.3, and I don't really have a problem with any bad navigation volumes. If you're not okay with paying to try out Locations Navigation, don't worry, you have a 1 month worldwide navigation license which you can activate and use for free without any restrictions.
Thanks for your 'input' Vious, but the issue remains no matter what satnav is used, premium or not.
It is a confirmed 2.3.3 issue with multiple threads on the google code forums
Sent from my Desire HD using XDA App
I hope they fix this soon. Such a GIGANTIC issue... i can't believe this isn't at all critical for them.
Same problem for me, Copilot support could not fix it for me also, claiming it was a problem with android not them. Used to work on Version 8.x.x.606
If this affects all versions of Android above 2.3.2 then it looks as if I have little choice but to buy an iphone or wp7 phone next, Google are unbelievable sometimes!
6 months and still no fix, I love Android and would hate to switch but this is a complete joke!!!
http://code.google.com/p/cyanogenmod/issues/detail?id=3165
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=794d84c209f5ad2d&hl=en
http://code.google.com/p/android/issues/detail?id=15690
I know this is an old thread, but I wanted to share my solution for this same problem that I've been having since upgrading to the new gingerbread. Note though that this is no longer an issue if you're using the latest google navigation app, but if you're like me and you like to use an offline nav app like CoPilot, then this solution should work for you.
Since this problem was introduced in gingerbread 2.3.3, I thought I would try replacing the libaudiopolicy.so library with one from a gingerbread 2.3.2 rom I had laying around and voila, that seemed to have solved the problem! I haven't tested this thoroughly, but it seems to be working so far. I hope this helps anyone else out there that is still suffering from this issue.
Could you post the file? Also, have you encountered any issues so far?
Perhaps post this in the previously mentioned google code pages for more testers....
Sent from my Desire HD using XDA App
Here you go! This one is for sense based roms.
No issues so far!!
Perhaps when I have a little bit more time, I'll post a link to this thread in those referenced google pages.
hexion said:
Here you go!
No issues so far!!
Perhaps when I have a little bit more time, I'll post a link to this thread in those referenced google pages.
Click to expand...
Click to collapse
Nice one I'll give this a try
I presume the libaudiopolicy.so file you posted is from a Sense ROM, it didn't work for me as I'm running BlackIce which is CM based.
Downloaded an early CM7 nightly based on 2.2.3, copied that file over and it worked!
I have updated the previously referenced Google pages.
Attached is the CM7 2.3.2 libaudiopolicy.so if anyone wants it.
rgrover said:
I presume the libaudiopolicy.so file you posted is from a Sense ROM, it didn't work for me as I'm running BlackIce which is CM based.
Downloaded an early CM7 nightly based on 2.2.3, copied that file over and it worked!
I have updated the previously referenced Google pages.
Attached is the CM7 2.3.2 libaudiopolicy.so if anyone wants it.
Click to expand...
Click to collapse
Yes, sorry, forgot to mention that. I've updated my post so now it won't confuse anyone else.
I'm glad the one from CM7 worked for you!
hexion said:
I know this is an old thread, but I wanted to share my solution for this same problem that I've been having since upgrading to the new gingerbread. Note though that this is no longer an issue if you're using the latest google navigation app, but if you're like me and you like to use an offline nav app like CoPilot, then this solution should work for you.
Since this problem was introduced in gingerbread 2.3.3, I thought I would try replacing the libaudiopolicy.so library with one from a gingerbread 2.3.2 rom I had laying around and voila, that seemed to have solved the problem! I haven't tested this thoroughly, but it seems to be working so far. I hope this helps anyone else out there that is still suffering from this issue.
Click to expand...
Click to collapse
Thanks hexion, you see this is exactly what I have been trying to say all this time - it must be something slightly changed in some audio file somewhere between 2.3.2 and 2.3.3 . I just have no idea about Linux / Android so never knew where to look for such things.
Now all we need is to compare these to see where the changes lie and try to patch the most current libaudiopolicy.so with only the previous Navigation settings, leaving all other new things as is.
rgrover said:
I presume the libaudiopolicy.so file you posted is from a Sense ROM, it didn't work for me as I'm running BlackIce which is CM based.
Downloaded an early CM7 nightly based on 2.2.3, copied that file over and it worked!
I have updated the previously referenced Google pages.
Attached is the CM7 2.3.2 libaudiopolicy.so if anyone wants it.
Click to expand...
Click to collapse
Hey rgrover, I'm also on CM7.1 Nightly. I tried renaming old file to libaudiopolicy.so.bak and copied the file you supplied into system/lib but now my device will not load past white HTC screen after reboot. Any advice?
UPDATE: it's OK it seems it was just a permissions problem. Everything working fine now
Hexion, you f**king treat !
My DHD is now pure perfection, with CM7.1 installed and this Sat Nav fix. Everything works at it should and I need nothing else from a phone (apart from battery life, but hopefully I can get Daemon Controller on CM7 at some point with better kernel).
If I had mone I would buy you a bottle JD (actually I would buuy myself one lol, maybe share with you XD )
Apparently, this fix for sat nav apps does not work for Google Navigation and TuneInRadio according to chykal1 on the google page. Music will not be lowered when the nav voice comes on. So if you use TuneInRadio a lot, you probably shouldn't apply this fix. Maybe when someone patches the latest libaudiopolicy.so, then we'll have a true solution.
Seems like the latest Crackle update has resolved issues with the A500 not being able to display video. I have been waiting on this for a while. (sorry if this has already been reported)
Nice ive been waiting on this...i searched but cannot find the new app, nor the update. Care to share?
Since it is a free app, I'm assuming it is ok to share it here.
Here it is...
Crackle
However, I only get audio, no video.
Running Taboonay 2.2
Anybody getting video?
nope...
btucker2003 said:
nope...
Click to expand...
Click to collapse
No video or sound for me, just black screnn.
I downloaded straight off the market.
Running taboonay 2.2 w/ richards 3.7.
Works but finicky on startup
Im running market version of crackle on stock 3.2.
Its kind of quirky.....if you open the app and choose your movie or show, you will then get a split screen. black screen with blue swirling circle at top and movie info at bottom.......when you see this just hit the home button to exit out of the app.
Then reopen the crackle app and wait a few seconds and the movie will start.
Tap on the movie to see the full screen button at lower right.
Works every time on my machine.
Since I'm still too n00b to post in the Dev Forum I'll post this here.
I just installed this awesome ROM and it all woks pretty fine... except for the bugs everybody has already mentioned in some topic or another.
About the bug regarding the capacitive buttons (the little Home/Menu/Back/Search) non correctly lighting up I found out a peculiar thing not mentioned by anyone else (afaik).
Maybe it could be useful, maybe not.
Anyway... in my phone (DHD ex-Cyanogenmod7, s-off, wiped) they are consistently turned off except when I open an ebook with Aldiko.
It always happens, and they stay ON untill I leave the ebook's pages.
It happens with both pdfs and epubs.
It only happens with Aldiko ... both Kindle and MoonReader failed to show the same glitch.
Just wanted to let people know u_u
Hasimir said:
Since I'm still too n00b to post in the Dev Forum I'll post this here.
I just installed this awesome ROM and it all woks pretty fine... except for the bugs everybody has already mentioned in some topic or another.
About the bug regarding the capacitive buttons (the little Home/Menu/Back/Search) non correctly lighting up I found out a peculiar thing not mentioned by anyone else (afaik).
Maybe it could be useful, maybe not.
Anyway... in my phone (DHD ex-Cyanogenmod7, s-off, wiped) they are consistently turned off except when I open an ebook with Aldiko.
It always happens, and they stay ON untill I leave the ebook's pages.
It happens with both pdfs and epubs.
It only happens with Aldiko ... both Kindle and MoonReader failed to show the same glitch.
Just wanted to let people know u_u
Click to expand...
Click to collapse
its look like kernel problem try diffrent rom on ur phone.
Maybe I will ... this ROM is still too raw (performance-wise) for me right now.
Browser navigation is quite slow and the overall phone is not very snappy (compared to CM7).
But my post was intended as a little help for the Dev Team ... maybe noticing this Aldiko glitch may help them understand where to put theor hands on the kernel.
Or maybe not XD
Umm use a different reader .if the lights stay on maybe a kernel issue just flash lords kernel from the dev section .failing that man use a devs Cyranogen infused rom
Sent from my HTC Desire HD using XDA Premium App
Forgot to ask what rom r u running
I used to run CM7.
With that rom the buttons were always ON, as they were meant to.
I usually use the Kindle app and it did nothing strange.
Then I installed (and am currently using) Virtuous Quattro RC2.
With this the buttons are always OFF, which is a bug.
Searching the forums I found out that this is a more or less common bug, and there is no fix for it right now.
But then I read an article about how awesome this Aldiko app is, and decided to try it along with MoonReader and a few others.
Doing this I accidentally discovered that Aldiko somehow "fixes" the button's bug.
Searching the forums it appears no-one else reported this thing to the Virtuous devs.
So I thought: if Aldiko "does something" that fixes the bug, maybe telling the Devs may help them look in the right place and find a solution or a workaround.
That is all
Also running that rom...after trying several. This seems to be the least buggy of all of...I have tried several. The 1beta4 (LC) was the quickest/smoothest. but I had numerous small but annoying issues and loaded Quattro on 1/23. I have an Inspire. I also loaded the Quattro wifi fix and had to load Lordmod for the sound to work..appears to be an issue with Inspire and ICS. Anyway, long story longer...I am also an Aldiko fan/user and don't have any issues with the buttons at all...maybe the difference in phone...or the 2 additional zips made it a non issue?
I'm now running RC3.
Wifi problem is solved.
Capacitive button problem is solved.
General lagginess appears to be solved.
Battery life seems better too.
Strange enough, there is no way to remove the 3g toggle from the task bar
Good job team Virtuous! :-D
Sent from my HTC Desire HD running Virtuous Quattro RC3 - with XDA App
Hasimir said:
I'm now running RC3.
Wifi problem is solved.
Capacitive button problem is solved.
General lagginess appears to be solved.
Battery life seems better too.
Strange enough, there is no way to remove the 3g toggle from the task bar
Good job team Virtuous! :-D
Sent from my HTC Desire HD running Virtuous Quattro RC3 - with XDA App
Click to expand...
Click to collapse
I have been running RC3 on my HTC Incredible S for the past few weeks and I never had any problem with the capacitive buttons until recently they stopped glowing and as you mentioned earlier they start working when I open Aldiko app. I read that the problem got solved for the RC3 then why am I having these issues?
Cornerstone is a multi windowed ui application that allows you to see and interact with 3 applications in the same window. Cornerstone requires changes to the framework so unlike other apps must be flashed and baked into a ROM.
Manufacturers website http://www.onskreen.com/cornerstone/
Development version (no root) v 0.85.1 (02/26/2012)
https://github.com/Onskreen/cornerstone/downloads
Team EOS cornerstone nightlies (w/root). http://goo-inside.me/devs/teameos/roms/cornerstone/nightlies
Main development Google group thread https://groups.google.com/forum/?fromgroups#!forum/cornerstone-dev
Does this work for WiFi xoom? I see an _1, does that mean it has improved already?
Question
Is it possible to get a md5 hash for the download file?. I assume we install the zip file with CW over the EOS nightly rom. Any info would be appreciated.
screwhead89 said:
Does this work for WiFi xoom? I see an _1, does that mean it has improved already?
Click to expand...
Click to collapse
Yes, this is for the wingray model. 0.85.1 is the newest version. Changlog is here http://github.com/Onskreen/cornerstone/wiki/Cornerstone:-Version-History
jdlaser said:
Is it possible to get a md5 hash for the download file?. I assume we install the zip file with CW over the EOS nightly rom. Any info would be appreciated.
Click to expand...
Click to collapse
Yes, I just flashed the zip on top of EOS rom. As far as md5, I don't know.
So if this if for the Wingray model, I assume flashing it over the EOS Stingray version would result in loss of mobile data? Has anyone tried?
See OP has been updated with EOS builds. There are stingray builds there. The EOS team needs to start a cornerstone nightlies thread IMO.
Wingray Cornerstone V1 here:
http://goo-inside.me/devs/teameos/roms/cornerstone/nightlies/wingray/Eos-wingray_cornerstone-1.zip
Installed it over Nightly 78, looking fine but with problems. No Lockscreen, no rotation, dpi was changed (think this is needed to get cornerstone working) with the result that some my icons are invisible on the homescreen. Thinks it´s going the right way, but at the moment...back to 78 Let´s see the next releases.
Flashed it over Stingray Nightlies 60, then I flashed Gapps 10.5 after for safe measure, works like a champ. No issues so far.
There is a Stingray version available but when I flashed it my 4g stopped working. I'm at work right now and can't connect to wifi but I will try when I get home. For now I am back on Stingray nightly # 63 but will be trying this on a regular basis until they get something that will work.
I'm pretty excited about finally getting a nightly for cornerstone
I flashed the Eos Cornerstone build and don't have the buttons to swap windows. Is this
something that's missing by design?
TIA
Swapping of windows has been removed.
https://groups.google.com/forum/?fromgroups#!topic/cornerstone-dev/AywAOOoZzFQ
double1 said:
Swapping of windows has been removed.
https://groups.google.com/forum/?fromgroups#!topic/cornerstone-dev/AywAOOoZzFQ
Click to expand...
Click to collapse
Installed over build #78. Working well, with the issues already mentioned. I will use it for a while and see what I think.
Team EOS does such a stellar job...we are really on the cutting edge.
On edit: the wingray Cornerstone build is a bit too unstable to use as a daily driver, but I can see that it is really coming along.
I've been running this for about a day over nightly #78 and there are a few issues that I've run into, but I'm going to continue using this as a DD unless the issues get worse.
Here are the problems I've encountered:
- the clock on the notification bar does not update. Because of the time not updating, third party clock widgets on the homescreen give a "Problem displaying widget" message
- Beating on Cornerstone (running memory hogs in all three panels) can make it force close. If it force closes, the only option is to reboot. If you try relaunching Cornerstone, the launcher force closes and Cornerstone never comes back up.
- Some WiFi issues. The notification bar shows me connected to a network that is well out of range and I cannot connect to a new network. I have to keep toggling WiFi on/off and I am eventually able to connect to another network.
- Stock live wallpapers do not size correctly - extremely zoomed in. For some reason, third party wallpapers work just fine.
- Lockscreen works sometimes and sometimes it doesn't
In addition to these problems, which are more of an inconvenience than catastrophic issues, here are some things that may be reported as "issues", but are not truly issues:
- the density of the main screen changes when Cornerstone windows are showing. Apps at the extreme right and left edges of the home screen will not show when the two extra windows are showing, but will show in full screen mode.
- if an app is coded as strictly a tablet app without resizing, it cannot run in the small windows, only the main panel.
- you can only run one instance of an app
EDIT: It looks like some of the clock/wifi issues were fixed by reflashing Cornerstone and GApps without wiping cache.
is anyone else's headphone jack not working now under the EOS Cornerstone nightly 1? Audio is playing for me through the speakers and only the speakers.
Sent from my Xoom using xda premium
I flashed the wingray nightly and I didn't have any problem till now!
The limit of only one instance for each app can be a little annoying but not a real problem.
If I won't find serious bugs this will be my daily
My headphones were working fine this morning when I was watching the Rum Diary on the train. I'll try to test with more apps later.
Edit: Confirmed, my headphones work across the board. Maybe a wipe and reflash is in order fir those having issues.
okantomi said:
Installed over build #78. Working well, with the issues already mentioned. I will use it for a while and see what I think.
Team EOS does such a stellar job...we are really on the cutting edge.
On edit: the wingray Cornerstone build is a bit too unstable to use as a daily driver, but I can see that it is really coming along.
Click to expand...
Click to collapse
I agree, but still, a very cool app with a lot of potential. Knocks out my Calender and gmail Widgets and apps. Force close problems. Would like to get window switching back. Uninstalled, until next update.
Alxoom33 said:
I agree, but still, a very cool app with a lot of potential. Knocks out my Calender and gmail Widgets and apps. Force close problems. Would like to get window switching back. Uninstalled, until next update.
Click to expand...
Click to collapse
I have been running cornerstone 1 over build 64 with no issues what so ever. Here's what I did when flashing from build 60. Flashed 64, flashed gapps 10.5, wiped cache and dev cache, rebooted. After reboot, rebooted back into recovery and flashed conerstone 1 and gapps10.5, wiped again rebooted and everything is working flawlessly. It is running extremely well with the kuma kernal by rogue. What I have found is if you are having issues with cornerstone just reflash it with gapps and it will usually fix the issue.
Sent from my Xoom using Tapatalk
I tried conerstone-2 and it worked OK for the most part but the HDMI interface did not move audio to the TV and left the output on the built in speakers. I will give the next release another look as I believe that it has advantages.
Sent from my Xoom using xda premium
p1rate7 said:
I tried conerstone-2 and it worked OK for the most part but the HDMI interface did not move audio to the TV and left the output on the built in speakers. I will give the next release another look as I believe that it has advantages.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Is anyone else having difficulty downloading the 2.0 rom?