yashsingh1/xdaforums huggingface dataset:
[G2 and Desire Z Android Development] kbeezie:
I uploaded the file temporarily to my server here: http://ionvz.com/share/gapps-jb-20120726-signed.zip

I double checked the MD5 checksum to match f62cfe4a827202899919fd932d5246d7 so it's the exact same zip.

---------- Post added at 05:29 AM ---------- Previous post was at 05:20 AM ----------

By the way just tried my DataSwap/SD-Ext enabler v1.2 on Build #61 and seems both are working fine.
[G2 and Desire Z Android Development] Sefy:
Mmm... what was changed? is the update important? i mean of course if there's a new version, there must be a reason for it ;)
[G2 and Desire Z Android Development] kbeezie:
v1.2 says on both the original post and in the reply exactly what was changed, and the only thing that changed was adding addon.d support (ie: the ability to upgrade a rom without having to reflash the add ons, but course this only works with roms/installers that supports /system/addon.d)
[G2 and Desire Z Android Development] rich0:
Warranty Law

Generally under US law (you might have MORE protection in any particular state, but not less), a company has to prove that the consumer voided the warranty by doing something that actually caused the problem. So, if the problem is the device won't boot and the cause is that the bootloader is corrupt, then you're probably out of luck. On the other hand, if the problem is that the device won't boot and the cause is that the power supply is defective, then legally they have to replace it.

That said, big companies break the law all the time, and if they do your only recourse is to sue them, or get the FTC to do it. Neither of those is going to be a great option for something as cheap as a phone. I've read stories about people being denied car warranty repairs costing thousands of dollars for not using OEM parts, which is a blatant violation of the Magnuson–Moss Warranty Act, but unless you're willing to sue and fight it out for years there isn't much you can do about it. If it happens enough a class action or FTC action will take care of the problem, but for rare problems companies can pretty much do what they want to.

It sounds like denying warranty claims for rooted phones is fairly standard practice, so while I can't agree that your warranty is void if you root your phone, the bottom line is that if your phone breaks and it happens to be rooted you're probably going to be taken advantage of. Half of the stuff you sign in adhesion contracts is likely to violate one law or another, and companies get away with it all the time.
[G2 and Desire Z Android Development] whiteghetto:
So, I have an ongoing weird issue that started with build 53.

I have installed every build so far and only had to wipe once. a few weeks ago.

Google for some reason thinks I am in Fort Worth Texas. I have seen it in News/Weather, Google Now and Facebook.

If I use Facebook Check In or Navigation, my location is correct

I just wiped, installed build 61, gapps and restore my user apps with titatnium backup.

It worked fine for a few hours, but again, is saying I am in Fort Worth

Any ideas?

EDIT, actually, even google nav is showing me in Texas.
[G2 and Desire Z Android Development] geojoking:
Is this happening when using Wi-Fi of mobile network? I remember that I once had a problem with my wireless router, it positioned me (all my devices) some 500-600 kilometers from where I actually was.
[G2 and Desire Z Android Development] dhkr234:
A disclaimer does NOT EVER alleviate anyone from the responsibilities laid on them BY THE LAW. If it DID, you would see people wearing shirts that say things like "if you can read this, I may murder you." or "Approach at your own risk". You think that would hold up in a court of law?

When you send them an email that says "My keyboard broke and I am running non-HTC build of android. Will you fix it?" -- OF COURSE they'll tell you to suck it!!!! IT COSTS THEM MONEY TO FIX IT. If you aren't smart enough to KNOW YOUR RIGHTS, they'll walk all over you.

Further, did you even READ that line? It says, VERY specifically, "resulting or caused by or from the unlocking". That does NOT say that the warranty on buttons falling out is void. It says that the SOFTWARE SUPPORT ****MAY**** (but not necessarily) be void. This is CONSISTENT with the law.
[G2 and Desire Z Android Development] kbeezie:
PS: You think you guys could maybe take all the warranty law debate out of the this rom-specific thread?
[G2 and Desire Z Android Development] whiteghetto:
after playing around with it, I do think its related to my LAN. though my IP whois info is correct.

How did you fix it?
[G2 and Desire Z Android Development] dhkr234:
Kaspersky? What in the world for??? :confused:

You know that it doesn't actually DO anything except consume resources, don't you?
[G2 and Desire Z Android Development] IsmailOmer:
Works pretty smooth... how come the SmartAss governer isn't available anymore?

And BTW do the devs know about some YouTube problem? Watch a video and see what happens!
[G2 and Desire Z Android Development] greed2:
i have my old problems !!! gallery not working !

may by some one can fix it ? :crying:
[G2 and Desire Z Android Development] geojoking:
I submitted my wireless router mac to Skyhook Wireless

http://skyhookwireless.com/howitworks/submit_ap.php

and after a while everything was back to normal.
[G2 and Desire Z Android Development] dhkr234:
Probably because that governor is a rather pointless mess. All it is, is INTERACTIVE with a capped (to minimum) frequency when asleep. You're better off with interactive since it doesn't force your frequency to minimum when asleep -- doing so causes problems with wake-up responsiveness and can yield an unresponsive call-answer screen, late ringing, failure to ring, or in the worst case, complete inability to wake up at all.

A better option is to use INTERACTIVE and use a sleep profile that reduces the maximum allowed frequency, i.e., to something ABOVE minimum, but within reason such that it actually will respond reasonably. As I read it, the power.vision.so actually does this.
[G2 and Desire Z Android Development] revanmj:
I have it on 61 too. Besides that, after using a camera in a third party app (for example Google Goggles) and trying to use it again without exiting the app it stops working - there will be a black screen instead of image from camera until you force close that app.
[G2 and Desire Z Android Development] blk_jack:
This is simply not true at all.

It doesn't cap your frequency whatsoever, but it does let you assign an ideal frequency for both screen on and screen off. This is helpful in that you can set your maximum frequency with screen on to say 1.2GHz but set your ideal frequency at 1.0GHz and it will aggressively try to hit 1.0GHz when the necessary load demands it and ramp down slower afterwards. It's a mixture between battery savings & performance since the same thing applies with the screen off.

Not only that, but smartassV2 lets you explicitly set a sleep wakeup frequency which it will automatically hit immediately on wake. From there it ramps up/down depending on the load. Even more reason for there to never be issues w/ wake-up responsiveness whatsoever.

Plus it lets you set very granular levels of ramp up/down steps and the frequency steps to take when going up or down (ie. jump 200mhz up at a time up and ramp down 100mhz at a time).

If you setup smartassV2 properly (which Andromadus does in the default 2.6 kernel), then it is an incredible governor and one of the most popular for a reason.
[G2 and Desire Z Android Development] Flinny:
did you ever post me that logcat?......
[G2 and Desire Z Android Development] J-Hop2o6:
Yes, this is a known issue. Works fine in portait, but weird in landscape (but you can still clearly see whats going on in the video).

Its fine here (after reboot). First time I opened it on 61 it didn't want to auto-rotate. I forced the rotate by opening up the kb, then closed it a bit after. After that it hot-rebooted on me. Works fine now tho :eek:
[G2 and Desire Z Android Development] nelsdzyre:
For youtube just disable hardware overlays in developer settings to watch in landscape mode.
[G2 and Desire Z Android Development] Sefy:
I just tried (didn't know YouTube wasn't included in Gapps), worked fine without any issues, rotated without sliding keyboard... just a bit of slow responding then i recall...

---------- Post added at 07:24 PM ---------- Previous post was at 07:21 PM ----------

Oh that explains why it worked for me then, i had that disabled when i read the first post :D
[G2 and Desire Z Android Development] J-Hop2o6:
I was talking about the Gallery app that had the rotate issue at first, not youtube. Youtube (and other video apps i'm sure) had the video issue in landscape. And yea, its weird GMail and Youtube isn't apart of gapps, even tho they are Google apps :rolleyes:
[G2 and Desire Z Android Development] Sefy:
I hope they fix the Gallery/Picasa thing... (btw: my Gallery app rotated without problem)
[G2 and Desire Z Android Development] pentie:
I can't get WIFI on after set off on 61:

logcat:

I have to reboot to connect to WIFI.
[G2 and Desire Z Android Development] SystemIcon:
Also can't turn wifi back on. Compass still has same issue.
[G2 and Desire Z Android Development] Sefy:
Now that you mention it, i experienced it twice today after flashing to 61... and i thought it was something i did...
[G2 and Desire Z Android Development] J-Hop2o6:
It happened only once. Reboot fixed it.
[G2 and Desire Z Android Development] MIkeRD03:
ICS / JB side-by-side comparison!

Build 61 seems to make a big difference when switching between apps so I was curious if this recent build is up to the latest ICS version. Luckily I have two identical DesireZ - one with build 61 and one with mimicry 1.3.2 / ICS 4.0.4 - so can make some real side-by-side comparisons. I guess it´s even interesting for the developer to see where he stands.

To be fair both mobiles are running with 1516MHz and the same launcher (Trebuchet).

The best to start with is booting - from complete off both versions seam to be quite identical until the Desire is ready to work. Now I tried different apps in the same order started together to see which one is faster. The picture here is not with every app the same most apps are started at the same time with minimal difference. Some rare apps are faster on ICS and a handful of apps are significant started faster on JB. My guess would be around 20-30% more speed. The good news is regardless how many apps I tried JB doesn' t go on his knees - this was different with build 53! Conacts and Phone is faster on JB. Maps and Currents is quite the same.

Amazing to see was Google Earth - it start much faster and zooming is really smooth here without any lag, wow! Mimicry is good, too, but zooming is a bit laggy in direct comparison. Over all build 61 feels a bit snappier and do react a tick faster, but it is not much difference. Both versions are fine!

Biggest problem with 61 in my eyes are the malfunctioning sensors like compass and acceleration besides the video bug. These two fixed would be a real milestone in giving our old DesireZ JB! Keep up that good work and thanx Flinny & your team!

Mike
[G2 and Desire Z Android Development] bradley_e_smith:
Interesting that you have 2 different radios on each device. I thought you needed the 19_M radio for any ICS/JB ROM
[G2 and Desire Z Android Development] blk_jack:
Did you disable the Virtuous OC Daemon before doing these tests? Otherwise the cpu would revert back to a maximum of 1.2ghz for your tests.
[G2 and Desire Z Android Development] dhkr234:
WRONG.

You just made an ass of yourself.
[G2 and Desire Z Android Development] blk_jack:
Don't just take my word for it, see for yourself.
[G2 and Desire Z Android Development] MIkeRD03:
No, let me know how to do it!
[G2 and Desire Z Android Development] blk_jack:
When you install Mimicry you can choose not to install the Virtuous OC Daemon, otherwise you can install an app like the OC/UV Beater to adjust the governors & frequencies of the CPU. If you don't, the Virtuous OC Daemon "takes over" that responsibility & as such your settings in the Performance section won't stick.
[G2 and Desire Z Android Development] dhkr234:
Did they never teach you how to read or something????

From YOUR link;

Screen-off frequency = typ. 245 MHz (min for whatever CPU it happens to be).

Translation:

This is INTERACTIVE governor with a HACK to hold down the frequency when screen is off.
[G2 and Desire Z Android Development] blk_jack:
First of all, I never said it wasn't a re-write of the Interactive governor, so I don't know why you're highlighting that.

Second, you're quoting the smartass governor, which has never been made available in any of our kernels, only smartassV2.

Third, with smartassV2 screen on frequencies are the exact same as screen off, not any greater. Just because it calculates an ideal frequency for screen-off (when not in deep sleep) doesn't mean it's a hack in any sense. What was accomplished in the original smartass has been refined in smartassV2 and there is more than enough evidence out there that it works well. You know, seeing as how there are numerous governors based off smartassV2 itself and the fact that a ton of ROMs use smartassV2 as their kernel's default.

Finally, you do realize that the CPU shuts off almost always when the screen is off, right? No matter what frequency you set as a minimum, if the phone is in deep sleep it doesn't matter because the CPU is completely off. The entire point of smartassV2 is to set an ideal frequency for when having to hold wakelock while the screen is off. That way if an app needs to scale up it's not held at a minimum frequency for an extended amount of time (thus using MORE wakelock/cpu/power) while still setting an "ideal" frequency so that it doesn't typically jump inappropriately high.
[G2 and Desire Z Android Development] roman.goncharenko:
Does anybody have a problem with Wi-FI? When I turn it On my Vision reboot after 2-3 minute.
[G2 and Desire Z Android Development] MarkyG82:
PS. Really happy to see a smiley button on the keyboard for texting again. Love it. :)

Edit: I too have an issue with turning wifi back on. Noticed in 53+.
[G2 and Desire Z Android Development] dhkr234:
Because THAT is what you were CONTRADICTING;

I think that's pretty clear.

Huh? I've seen that option listed by SEVERAL kernels, but more importantly, that was the question ***I*** was responding to. It was asking why SMARTASS wasn't available. Nothing about SMARTASSV2.

NOBODY ASKED ABOUT V2!!!!!

That's nice...

Obviously, what's your point?

As you say, there are times when the CPU is ON while screen is off.... during which time, the governor is AFFECTING the CPU speed.

But again, you're talking about V2, which is NOT the subject of discussion.

"Inappropriately high"????

Do you have any idea how that sounds? There IS NO "inappropriately high". The frequency is set based on the workload. Unless you feel like keeping the CPU from deep sleeping and draining the battery... that your objective?
[G2 and Desire Z Android Development] hendusoone:
I flashed 61 to my phone today, pretty sweet. Just going to echo a few things from other posters - picasa albums aren't showing up in gallery (I checked the sync google photos box in my google account settings), and on initial launch of the camera the preview is distorted and rotated 90 degrees (but it corrects itself after taking a picture).

Now, this is a really weird issue, but I was able to work around it:

In Terminal Emulator, I remounted /system as rw, then issued this command:

cp /sdcard/LookAtMe.ogg /system/media/audio/notifications/

The file was written to /system/media/audio/notifications/LookAtMe.ogg, but the notification sound would not play when selecting it from the menu, and attempting to play the .ogg file in ES File Explorer results in a 0 second length audio file and a red name in the playlist. Playing the file from the /sdcard/LookAtMe.ogg location worked correctly. After inspecting the file properties in ES File Explorer, I discovered that the file was copied with incorrect permissions set. Changing the permissions from rw------- to rw-r--r-- fixed the issue. So... is there something wrong with the cp command? Or is this an expected behavior?
[G2 and Desire Z Android Development] blk_jack:
Derp.

I think it's safe to say that somebody mentioning smartass in a test builds thread is referring to the only smartass governor that's ever been in an Andromadus ROM (smartassV2). Not, you know, some ancient version of smartass that hasn't been used in any Andromadus/ICS ROM let alone JB.

My response which you said was "wrong" mentioned smartassV2 specifically twice. Plus I followed up my "That's not true" comment by specifically pointing out every single thing that was wrong, including the notion that smartassV2 (and the original) are capped in any way.

I'm done cluttering up this thread by replying to some troll who's post history consists almost entirely of over-reactive freak outs that offer nothing of value to the android community. Sorry folks for having to read that ;)
[G2 and Desire Z Android Development] J-Hop2o6:
Same using 61. You have to reboot (make sure wifi is turning on before reboot) for it to work. Worked fine with previous build(s).
[G2 and Desire Z Android Development] jspina:
Hey flinny don't forget to take issue number 1 out of the first post. ;)
[G2 and Desire Z Android Development] SystemIcon:
can those wishing to discuss overclocking please take that discussion somewhere else? I would like to see this thread remain focused on Flinny's rom, so that when users provide feedback like in matters of wifi not working after turning it off and back on, or the compass not working, Flinny can see that feedback instead of folks arguing the merits of CPU governors.
[G2 and Desire Z Android Development] Tmender:
In build 61, it appears that the alt key on the keyboard does not work in the browser, I am unable to type in any numbers using the Hardware Keyboard. Swype works fine though. It appears the address box works, but any other Alt or Caps typing in browser (so far) does not work.
[G2 and Desire Z Android Development] Flinny:
Yeah Have been meaning to update that. Could also remove Camer flash as of next build but it seems I never added it in the first place!
[G2 and Desire Z Android Development] thebogmonster:
I'm guessing you've managed to find the flash problem then Flinny?
[G2 and Desire Z Android Development] spjuggalojoe:
So far 61 seems to be a big improvement. I still have a few issues going on from 53, though, even after super wipe. Talk will not sign in, notifications from G+ and Gvoice not working, including txt on voice (like its not syncing) and capacitive buttons sometimes seem unresponsive. I have redownloaded, checked and reflashed gapps for talk problem to no avail. This is second time I've asked about talk and voice, does anyone else have these issues or have any solutions?
[G2 and Desire Z Android Development] jspina:
Seems to work for me but I have an older version of the gapps
[G2 and Desire Z Android Development] J-Hop2o6:
Well its time to retire the G2/DZ. Just got home from work to my brand new Galaxy Nexus waiting for me to tinker with it. Its been fun, but its time to finally move on. I would like to thank the CM team & Andromadus team for pumping new life into our outdated G2/DZ. Good luck with the JB development! I'll test them out from time to time to see the teams progress.
[G2 and Desire Z Android Development] spjuggalojoe:
Yeah think I might go back to the last version. Had to do that thru a few of the Andromadus betas if I remember correctly. Still can't figure out text message sync on voice, its almost like background data isn't working, even though its enabled. Phone number is correct too. :(

Edit: alphas
[G2 and Desire Z Android Development] blk_jack:
Good luck man, hope to run into you again!
[G2 and Desire Z Android Development] J-Hop2o6:
Thx! And I hope so too :D
[G2 and Desire Z Android Development] Sefy:
I just had a weird thing happen... in the middle of writing on SMS... phone didn't respond... i thought it's just slow typical freeze.. then it booted :confused:
[G2 and Desire Z Android Development] rirozizo:
check your battery connection to the phone (those golden things)

———————————————————

i didn't mean to mock you or to offend you in any kind of way
[G2 and Desire Z Android Development] Sefy:
Battery connection is fine, i've also been using the phone for the last few days, this is the first reboot during the typing of a message.
[G2 and Desire Z Android Development] whiteghetto:
Thanks a ton :)

I am in the process of submitting my MAC and location. I do hope this helps.
[G2 and Desire Z Android Development] Formiak:
http://www.xda-developers.com/android/usb-otg-for-the-htc-sensation-on-ics-sense-roms/

Do we also have that feature on 3.0 kernel for Desire Z ? Or even is it possible to have in future? Can't check myself as for now I don't have such cable.
[G2 and Desire Z Android Development] Flinny:
It's compiled in already but probably missing some additional drivers and rom support. I don't have a cable either :)
[G2 and Desire Z Android Development] greed2:
to Flinny . logcat

gallery problem
[G2 and Desire Z Android Development] nivlac978:
This works a lot better for me than ICS ever did. A couple glitches here and there but at least I can browse the internet without it freezing up and rebooting.
[G2 and Desire Z Android Development] sp1980:
There seems to be something wrong in the mediaframework. The result is that Xiia Live doesn't properly handle AAC+ streams. Are there more people dealing with this issue or something comparable? I posted the details about this bug in the bug-tracker. http://bugs.andromadus.com/issues/82
[G2 and Desire Z Android Development] Flinny:
Strangely enough I had this problem today.... all of my media disappeared after a crash when I was testing something. No amount of wiping or killing data would get it back... eventually I copied everything off my SD card and formatted it and now all is good again....
[G2 and Desire Z Android Development] MaxWiz:
I had this issue and found this solution. It does work but when I added some more tunes later they are never found.

My current solution is to use CMs CoolGallery3D and am using poweramp for tunes. Both work perfectly and always find the media.
[G2 and Desire Z Android Development] Flinny:
Build 69..

Off the top of my head without looking as I don't have time... :)

Camer Flash works (fyodor)

Hardware video decoding mostly works, few issues left and the overlay problem we had already that causes the flicker (Flemmard)

Camera Preview is the right way round again (yay I fixed something...)

power.vision.so max freq set at 1.2, if you want higher/lower push one of the alternate ones in the OP.

Loads of CM merges from yesterday...

As always check the repo's if you're that interested :)

Nick.
[G2 and Desire Z Android Development] blackknightavalon:
Had a similar issue with TuneIn Radio cutting off the stream after a few minutes. I'm going to see if flashing build 69 helps.
[G2 and Desire Z Android Development] .ili.music.ili.:
What is the link for the repo?
[G2 and Desire Z Android Development] captainreynolds:
This. I've looked and wondered but always too afraid to ask.
[G2 and Desire Z Android Development] olearyp:
https://github.com/andromadus & start exploring!
[G2 and Desire Z Android Development] pentie:
confirm 69 fixes the WIFI / camera preview rotate problems.
[G2 and Desire Z Android Development] sp1980:
Build 69 does not solve the AAC+ streaming problem, but you cannot assume that the devs fix it that quickly. Overall very nice progress!
[G2 and Desire Z Android Development] blackknightavalon:
True. This is stable enough for every day use, but my media's not being read by any of my music players. I'll need to reformat my SD card when I get home.

Sent from Spaceball One.