yashsingh1/xdaforums huggingface dataset:
[G2 and Desire Z Android Development] tiger2wander:
Just curious about kernel 3.0. I checked on htcdev.com and see that HTC One S & V has kernel 3.0.x. I though that phone has some specs similar to our device.

So can we use some part from it to improve Desire Z/G2 ROM?

Will be try flinny3_26 soon as it downloaded to my machine :)
[G2 and Desire Z Android Development] Flinny:
Primou is one V. That is the base of the kernel source that has been used. It's adding all of the drivers that are not included. And the important bit board-vision* that has been the work.

Nick
[G2 and Desire Z Android Development] tiger2wander:
Cheer, flashed 3.x kernel and it work just very well at this stage. I have switch from AOKP rom which used with Elitemod kernel and it work fine, only need to clear cache & dalvik cache after flash this ROM.

Also, got very good performance with CPU set to: 245 ~ 1516 Mhz ondemand mode

- AnTuTu benchmark: 3222

- Vellamlo: 1174

- Linpack: - Single: 43.258 - Multi: 38.676

- Quadrant: 2469

Will be stay with it for a while to see how stable it is :)
[G2 and Desire Z Android Development] cucisan:
ics runs as fast as GB on the nexus s with 512mb ... apploading/multitasking is no problem there... so the ramsize shouldnt be the Problem...
[G2 and Desire Z Android Development] jspina:
I just installed the new kernel and all seems to be good over here as well. Gaming with nova 3 seems to be a little better and camera takes some good pics. :D:thumbup:
[G2 and Desire Z Android Development] PooN_HeaD:
just to let everyone know, all the Jelly Bean apps going around, work on this rom. I have the new play store and google now (although voice doesn't work which is a known issue)

T-Mobile G2

.19 radio

Flinny's test build 99
[G2 and Desire Z Android Development] cnote74:
Anyone have a link to the 3.0 kernel?
[G2 and Desire Z Android Development] bradley_e_smith:
Look at the first post.
[G2 and Desire Z Android Development] DeathName:
What about wakelocks with 3.0 kernel? The only reason for not switching to ICS for me is bad battery life.
[G2 and Desire Z Android Development] thebogmonster:
3.x Kernel

Just got to say well done to Flinny and the others for getting a 3.x kernel working!

Considering the obstacles you guys faced (which I'm sure a lot of users will not realise) this is a great bit of work and I'm amazed how stable it actually is!

Nice one - I've used it as the DD for my 2nd DZ for a day now and it's not actually caused any issues.

Am even quite liking the long press trackpad to wake side effect - maybe should be a selectable option!

again well done!

::D

EDIT : Wireless N works well - connected to an AP running N only and no problems at all.
[G2 and Desire Z Android Development] Broman400:
Is the 3.0 kernal usable with the Sense 4 Beta 7 ROM?
[G2 and Desire Z Android Development] Flinny:
Not really bothered about sense roms myself tbh ;-) It's not a plug in replacement either way unless the hardware it's coming from is basically identical to the DZ.

3.x rom update shortly if the changes pass a cursory testing.
[G2 and Desire Z Android Development] Flinny:
Enabled QCOM_LPA - Low Power Audio.

Enabled QCOM_KERNEL_ROTATOR_FORMATS - should fix some landscape video issues.

Enabled some other QCOM_AUDIO flags...

Switched init.msm7x30.usb.rc to use usb function switches.

Enabled MTP and PTP (toggle which one you want to use in Settings->Storage->Menu key->USB computer connection)

Enabled wireless N in framework and started using abgn firmware

Cleared out some old stuff from BoardConfig

Camcorder still b0rked, still a bit of lag waking up from power button/trackpad

CM changes to current.

Tweaks (obviously)!

Seems a little faster and smoother to me...

As so much has changed around audio it's probably best to test stuff you use see if anything's broken :)

Nick.
[G2 and Desire Z Android Development] virtualflyer:
this is sooo good. 3.0 is out when my phone is out (warranty repair...)

Does usb host work?
[G2 and Desire Z Android Development] Flinny:
<*> Support for Host-side USB - not tested but it's built in.

Also just fixed wifi-direct for the next build, will check that it works at home first :)

Nick.
[G2 and Desire Z Android Development] virtualflyer:
looking forward to trying it... This is so amazing... I bet this time, when someone finally almost managed to get it to work, htc will send me a new phone which of course won't have usb host...
[G2 and Desire Z Android Development] imanoob:
Music cannot be played after lpa addition. Crashes and causes a reboot unless it's over Bluetooth.
[G2 and Desire Z Android Development] mintaeroboy:
Does anyone have working / not working list for 3.0 kenrel?
[G2 and Desire Z Android Development] arzkkr:
Netflix showing no picture, only a black screen, audio is working (after full wipe)?
[G2 and Desire Z Android Development] D3V!Lc0r3:
My acutual installed Andromadus Mimicry v1.1.2 brings 3286 in AnTuTu Benchmark with only 1,2 GHz ;)
[G2 and Desire Z Android Development] Flinny:
I get about 3800 antutu with 3.x at 1.5ghz. With 2.6 I got about 4000 at 1.6. I should flash back a 2.6 and do some tests at 1.5 to do proper comparisons but apart from the first press of power and trackpad not registering when the phone is in sleep and camcorder not working this behaves better than testbuild 99 for me. The audio Issue with lpa I'll look into shortly. I do usually play via bt but sure I tested it on speaker as well.
[G2 and Desire Z Android Development] tiger2wander:
@Flinny: Would you make a separate package for Kernel 3.0 only? I want to test it with some different ROMs. Because of Andromadus ROM make my phone hot & slow because of default browser make CPU run too high and drain battery too quick.
[G2 and Desire Z Android Development] xT4Z1N4TRx:
Alright, cheers mate :-)
[G2 and Desire Z Android Development] shortlived:
Oh yea? I found some files to get it working on these here forums. I have not tried it with this rom yet but I think I will try it a little later today.
[G2 and Desire Z Android Development] blk_jack:
There are reports that it's partially working, but from what I've heard it introduces a ton of issues. Let me know if that's not the case of course, just tellin' you what I heard :)
[G2 and Desire Z Android Development] ubernicholi:
im on build 45, and i cannot get the onscreen keybored to display while in chrome. i can use it on the address bar, but not on pages, such as this box. also happened on 44, both fresh installs.

here is the logcat line.

04-19 11:05:28.852: W/LatinIME(1535): Unexpected input class: inputType=0x00000000 imeOptions=0x02000000
[G2 and Desire Z Android Development] tpayne1:
Good thing that will be next week with the release of the One S.
[G2 and Desire Z Android Development] shortlived:
Update on wifi calling. The patch I was referring too earlier did not work. So oh well.
[G2 and Desire Z Android Development] timskyline86:
Which patch was you referring to?

Vision wifi call 4.0?

I worked on that and jerl built it for me. It's just libs from GB, apk and updates the build.prop

It will be easier to wait for the libs from T-Mo, but its not neccesary I don't think. I can't narrow it down as to how the DHD has it working on their ICS roms. Been looking into it and playing around with the libs from others.

I've made improvements. Now I can't keep it from force closing after a call and the handset speaker cutting out when the prox sensor turns the screen off.

I have discovered that if you kill the app during the call to hang up, it will reconnect and work again until you hang up normally.

Been looking through the logcats but I'm a novice at this so its pretty much like reading a different language to me.

I do think though its both the lib and something in ICS itself that's causing it to fc.

But I've given up with ICS coming out from TMO, and just waiting on that.
[G2 and Desire Z Android Development] David Dee:
Full day of testing 45, and all is working. Consistent with other posts above, I have experienced an approximately 15% increase in battery life, given same use, from B2.

As I am writing this post my phone just rang but the screen did not turn on. Even after ringing, the green light flashed but the screen stayed blank...could not get screen back on until a reboot. Has never happened to me on any Andromadus build.
[G2 and Desire Z Android Development] blk_jack:
This has been fixed (as well as the screen draw delay when the phone is ringing), will be in the next build!
[G2 and Desire Z Android Development] David Dee:
Cool. I have always had the screen draw delay, but this complete screen blackout has never occurred. Is it a problem unique to this build?

Sent from my Desire Z using the XDA App
[G2 and Desire Z Android Development] blk_jack:
I think so, I don't recall offhand where it was introduced, only that it's been fixed :)
[G2 and Desire Z Android Development] SoTacMatt:
This has been running well for me all day!
[G2 and Desire Z Android Development] shortlived:
the files I tried that did not work was the ones linked too from virtuous primadona unofficial thread, I would link it but its hard on mobile
[G2 and Desire Z Android Development] virtualflyer:
There is also a delay between the moment when you see the number calling and when you see the person calling at least sometimes. Didn't get it with test builds, but surely with alpha or beta...
[G2 and Desire Z Android Development] philippecr:
Will check this test build out to see if tis fix the WWE keyboard layout... (ya the FN+ ? key doesn't gives me " )
[G2 and Desire Z Android Development] :
information

looks like nexx is working on a 3.0 kernel based on one v sources for the htc desire s...

maybe this is also interesting for our device:

https://github.com/nexx/htc-kernel-msm7x30-3.0
[G2 and Desire Z Android Development] shellin:
Just curious: what are the benefits to having a 3.0 kernel?
[G2 and Desire Z Android Development] mesaj:
Can I flash this ROM over Andromadus Audacity 2? Dalvik & cache wipe could help avoid bugs, like with ILWT.

BTW.

@Flinny,

Can you make something to prevent phone from rebooting while playing more demanding 3d games? GTA, Shadowgun result in phone crash then restart.

I'll stay with Andromadus, but this is only thing I found annoying and because of this I wanted to switch back to ILWT.

Other bugs:

*Fn+1,2 in Chrome was reloading previous website (Back), I don't know it's working as intended, but IMO it isn't when I can't type my password and login which has "1" char in it and page changes to recent.

*Camera preview was buggy with Google Goggles app, but codes were correctly scanned.

*Text of screen icons, widgets, app drawer was sometimes strange, but just for a moment then it was going back to it's standard state, I'll include screenshots later.

I know there are some improvements according to AAb2, so maybe something is fixed, but I'll test it now and check by yourself.

PS. Please change link from first post to download latest version testbuild v47 http://www.flinny.org/testbuilds/flinny47.zip or just to view entire directory http://www.flinny.org/testbuilds/ so it has list of all available downloads
[G2 and Desire Z Android Development] :
We probably dont need the camera hack anymore ;)
[G2 and Desire Z Android Development] virtualflyer:
For example it seems that usb host works flawlessly with 3.0 kernel, and this is enough for me ;)

For the ? bug, I've managed to solve it and posted on beta thread the right layout at least for italian language, but it's the same for the others... If there's a better way to send the fix to developers, I'll do it...
[G2 and Desire Z Android Development] blk_jack:
Not entirely possible. The 3.0 kernel+wifi module require that some of the framework be specific to it.
[G2 and Desire Z Android Development] dhkr234:
MMS: Routing issue?

Ok, now in Android 2.x, to send an MMS, it would disconnect the data APN and connect to the MMS APN. When finished transferring the MMS, it would disconnect from that APN and connect back up to the data APN. It could only be connected to one APN at a time.

Android 4.x is able to connect to multiple APNs simultaneously, it would seem in an on-demand way. It is no longer necessary to disconnect from the data APN in order to connect to the MMS APN.

That is a good thing, IF everything got routed correctly.

This is what I'm observing for MMS sending:

root@android:/ # busybox route -n; busybox ifconfig
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 10.200.30.209 0.0.0.0 UG 0 0 0 rmnet0
10.196.128.56 0.0.0.0 255.255.255.248 U 0 0 0 rmnet1
10.196.128.57 0.0.0.0 255.255.255.255 UH 0 0 0 rmnet1
10.200.30.208 0.0.0.0 255.255.255.240 U 0 0 0 rmnet0
10.200.30.209 0.0.0.0 255.255.255.255 UH 0 0 0 rmnet0
74.115.197.68 10.196.128.57 255.255.255.255 UGH 0 0 0 rmnet1
74.115.197.69 10.196.128.57 255.255.255.255 UGH 0 0 0 rmnet1
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:32 errors:0 dropped:0 overruns:0 frame:0
TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2284 (2.2 KiB) TX bytes:2284 (2.2 KiB)

rmnet0 Link encap:Ethernet HWaddr 9A:08:4D:0D:CC:C7
inet addr:10.200.30.215 Bcast:10.200.30.223 Mask:255.255.255.240
inet6 addr: fe80::9808:4dff:fe0d:ccc7/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:2000 Metric:1
RX packets:377 errors:0 dropped:0 overruns:0 frame:0
TX packets:483 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:200173 (195.4 KiB) TX bytes:57025 (55.6 KiB)

rmnet1 Link encap:Ethernet HWaddr 32:71:6B:F4:BC:9C
inet addr:10.196.128.59 Bcast:10.196.128.63 Mask:255.255.255.248
inet6 addr: fe80::3071:6bff:fef4:bc9c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:2000 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:960 (960.0 B)

root@android:/ #

Please note that the configured MMS PROXY is 74.115.197.70

Notice anything funny about the masks on the routes assigned to rmnet1 interface? In fact, with that mask, the address of the MMS PROXY will be routed through rmnet0 rather than rmnet1!!!!

Destination 74.115.197.68 should be masked 255.255.255.252 rather than 255.255.255.255.

Now of course, this explains perfectly why MMS works when you make the MMS APN selectable and select it, because doing that DOES disconnect the APN, and resets the default route to use the MMS APN, hence any IP that doesn't have a good route assigned will be routed over the correct interface anyway.
[G2 and Desire Z Android Development] heathenasparagus:
Would you recommend this for users of the cm9 unofficial rc1 ? (link in my signature)

can you please link to a guide on how to replace the kernel ?

Thank you
[G2 and Desire Z Android Development] Flinny:
The 3.x kernel is in a complete rom, there are framework changes and init changes required for the new wifi etc. It's not just a kernel to flash with other rom's.
[G2 and Desire Z Android Development] osho741:
So when the other apn is selected its using the. 248 mask instead of the .255 mask? The. 68 address isn't in the same address space as the. 70 proxy? Rather the issue is with a .255 mask it has to go through rt0 because it doesn't have another route?
[G2 and Desire Z Android Development] dhkr234:
Its not a question of being selected, its a question of being CONNECTED. MMS APNs are not selectable. When you are trying to send an MMS, Android is supposed to automatically connect to the MMS APN (now without disconnecting the data apn), and create a new route in the routing table to direct MMS protocol through the MMS APN to the MMS PROXY.

The problem is that the .68 destination is a HOST destination and not a NETWORK destination.

What that entry in the routing table says, is that any traffic directed to 74.115.197.68 will be routed via the 10.196.128.57 gateway on rmnet1.

rmnet1 is the MMS APN NETWORK. In order for an MMS to be sent, it has to be sent via rmnet1.

As the routing table shows, the MMS PROXY will be routed through rmnet0, since the gateway for rmnet1 is a HOST ADDRESS and not a NETWORK ADDRESS.

The difference between a host address and a network address is that the host is the specific machine to which traffic is targeted.

A network address is one where the ending bits are 0's to the full network address space.

For example NETWORK ADDRESS of 11111111 11111111 11111111 00000000 with NETMASK 11111111 11111111 11111111 00000000 includes all IP addresses from 11111111 11111111 11111111 00000001 through 11111111 11111111 11111111 11111110 (the last is reserved as the broadcast address, hence stops at 11111110

So as I've mentioned, if that .68 route had a netmask of 11111111 11111111 11111111 11111100 (255.255.255.252), then the destination address would be a match against that network and be therefore routed over rmnet1. Since it is not a match, it is routed over the default route, which is not authorized to deliver MMS messages.

x.x.x.68: x.x.x.01000100 --> last two bits "00", IP addresses in that network are 01000101 (x.x.x.69), 01000110 (x.x.x.70), with 01000111 (x.x.x.71) being reserved for the broadcast address.
[G2 and Desire Z Android Development] mesaj:
I've installed version with kernel 3.0 and phone randomly reboots when I want to play music with Apollo.

Flinny, can you add 1306MHz option to OC? This is highest stable in all ROMs for me, on 1400MHz sometimes I need to pull battery, as it's too high, and 1200MHz is good, but that additional 100MHz makes difference a bit. I'll try if GTA3 & some other games still stucks on 3.0 kernel, on 2.6.35 it was after 2 mins of gameplay, and because of this and worse battery life, I can't switch to ICS from CM7.
[G2 and Desire Z Android Development] Flinny:
#Low Power Audio

lpa.decode=true

lpa.use-stagefright=true

Remove those lines from build.prop for now it's causing issues with playing music when your using speaker or headset.

As for the OC option, there are other more important things to sort at the moment, once things have stabilised a bit then we can look at it.

Nick.
[G2 and Desire Z Android Development] dhkr234:
Any comments on the MMS routing problem????
[G2 and Desire Z Android Development] iplexus4:
maybe later you can add fm transmitter? i know it bloody hard but, maybe... later? and what do you think about settings for audio output? (music speaker\cal speaker\both for music)
[G2 and Desire Z Android Development] Flinny:
I have been reading them... not had a chance to look at it properly as I've been playing with something bean related... Off the top of my head I can't see where the problem would be device specific, may even be an upstream bug but can't say for sure at the moment. Does the same problem also happen with the CM9 rom and AOKP?.
[G2 and Desire Z Android Development] dhkr234:
It is upstream all the way to AOSP. There are even upstream bugs against Nexus S with factory image, but apparently nobody is interested in it upstream. It affects ALL CM9+ devices, which includes my wife's Doubleshot (which was also affected under AOKP prior to the availability of CM9).

http://code.google.com/p/android/is...s Owner Summary Stars&groupby=&sort=&id=23233

Now there is definitely some inconsistency in the effects of this bug -- it only affects certain carriers and in certain circumstances;

1) The carrier has separate data and MMS APNs.

2) The MMS Proxy authentication is by network route, i.e., via the MMS APN's gateway.

In some carriers, the MMS Proxy will accept routing through the data apn gateway as sufficient authentication.

The end result is that this bug affects only a subset of service providers, and in some cases, you can kludge your way around it with a combined APN.
[G2 and Desire Z Android Development] scanno:
Open the zip file, take out boot.img and replace the boot.img in the cwm zip of the from you want to test... That will work unless the ramdisk requirements differ... But that is more advanced 'hacking' :D. Oh no, that will not work, because there is a version check in the wifi drivers.... If you change the kernel version, you need to recompile a couple of modules. One of them is the wifi module/driver. It will be more advanced hacking...

Verstuurd van mijn VegaCream RC1 met Tapatalk
[G2 and Desire Z Android Development] sorceforge:
As Flinny said, framework need to be changed in order to enable Wifi. I have tested a thing that you said (including modules), but I failed to turn on Wireless LAN.
[G2 and Desire Z Android Development] spjuggalojoe:
sync problems

Just flashed '3_30.zip and gapps, now play store is not syncing my apps. Usually it starts syncing before I can uncheck the "Auto-add Desktop Widgets" feature, leaving then only to restore settings with Titanium. I've searched this and the main Audacity forum and haven't found this issue. Can anyone help? I only backup settings with Titanium, and really don't feel like clicking each of 200 apps on play, install, install, ok, back, next app argh!
[G2 and Desire Z Android Development] tarroyo:
When will there be a daily driver build available? I'd like to try out the 3.0 kernel that I've been reading so much about.
[G2 and Desire Z Android Development] yozgatg:
If u take a look at github, you'll see flinny is working on jellybean 4.1.

I don't think there's any point in getting a perfect ICS rom, the ones with 2.x kernel are pretty usable daily drivers. It's much better to start working at JB, since I guess most porting stuff will be reusable and as such it shouldn't take that much time. Compared to the ICS roms that is, that took like 5 months to get a proper, daily working build
[G2 and Desire Z Android Development] Flinny:
Shortly... :)
[G2 and Desire Z Android Development] spooke:
Awesome, would that be tonight? :p

Really glad we have you guys and the other devs keeping this phone alive!

Edit - F5'in like crazy lol..
[G2 and Desire Z Android Development] pauldacheez:
Wait, what, it's semi-stable that quick? And with a 3.0 kernel? Holy ****, Flinny/CM Team, you guys are amazing. <3 <3 <3
[G2 and Desire Z Android Development] shellin:
I agree, that was crazy fast. Flinny, I haven't had the chance, but I want to thank you and the rest of the team for such incredible work on our devices. You helped keep our phones alive and I don't think the thanks button would be enough :)
[G2 and Desire Z Android Development] Flinny:
There are issues around keyboard/capacitive button/notification LED lights... auto brightness etc.

There are issues around microphone outside of calls.. (yes again...)

Camera doesn't exist in these builds never mind work :)

It's a very early CM10 so if something doesn't work, crashes we probably know about it already.

Audio, Data, Wifi, Bluetooth all work.

Still some work to do around QCOM OMX etc.

This whilst I have been running various versions of it for the last day or so is probably not really a DD yet!

Backup/Flash have fun with it by all means :)

Will post the link once I've done some final tests and it's finished uploading.

Seems there is still a problem where it will sometimes bootloop... just reboot it until it loads, seems to be something to do with audio.
[G2 and Desire Z Android Development] tarroyo:
Very exciting to see development towards JellyBean moving so fast, VERY EXCITING INDEED!
[G2 and Desire Z Android Development] Dukenukemx:
Still, that's very impressive. :victory:
[G2 and Desire Z Android Development] spooke:
I'll give it a try tomorrow, but probably won't use it as a daily until most of the 'minor' bugs are fixed. Still can't believe we already have a really good Jelly Bean rom :)
[G2 and Desire Z Android Development] tiger2wander:
It's really amazing for fast forward. Will be try soon.
[G2 and Desire Z Android Development] PooN_HeaD:
so are you still going to work on the 3.0 kernal for ICS, or has that ship sailed right into JB? Because a completely stable 3.0 kernal would be great, for now...

T-Mobile G2

.19 radio

Flinny's test build 99
[G2 and Desire Z Android Development] Whoareyou:
jfyi, its spelled "kernel", in fact, kernal isn't a word :P