[ROM+Kernel][CM-11.0][4.4.4][OS2SD/internal][f2fs]bigsuperROM-thunderc-4.4.4

[yaconsult]

Re: It's my thread and I'll b*tch if I want to...

Connecting to google play seems to sync the clock. I did a search and ended up installing the free ClockSync from the market and it has lots of nice options for how often to sync the time. What interval would those of you using this rom recommend? That is, how long does it take for the lag to become noticeable/bothersome?

 

[bigsupersquid]

Re: [ROM+Kernel][CM-11.0][4.4.2][OS2SD/internal]OV-KitKat (JBC based)

Connecting to google play seems to sync the clock. I did a search and ended up installing the free ClockSync from the market and it has lots of nice options for how often to sync the time. What interval would those of you using this rom recommend? That is, how long does it take for the lag to become noticeable/bothersome?

My clock issues have always been somewhat random. More ofte after sitting idle a while, sleeping. Screen on charging helps but isn't infallible. Even leaving the analog clock on screen while charging doesn't guarantee the alarms go off.

I read kit kat has new alarm API and older SDK version apps default to the old api which may refuse to wake. Dunno if that applies or not.

 

[Melvin Jefferson]

Re: [ROM+Kernel][CM-11.0][4.4.2][OS2SD/internal]OV-KitKat (JBC based)

The latest version of Google+ has been out for a while yet still isnt compatible with this rom/kernel

I guess google is not letting up on this issue

 

[bigsupersquid]

Re: [ROM+Kernel][CM-11.0][4.4.2][OS2SD/internal]OV-KitKat (JBC based)

officially, google stopped supporting armv5 as of ics. They never supported armv6 at all... now almost all gapps are built for armv7, d any with thumb2 assembly crash "legacy" s CPUs like ours.
Honstly, I'm surprised that any new gapps run at all since there's basically zero support. The things that still work, google hasn't tried to optimize for speed yet.

The latest version of Google+ has been out for a while yet still isnt compatible with this rom/kernel

I guess google is not letting up on this issue

 

[Shinkenred]

Re: [ROM+Kernel][CM-11.0][4.4.2][OS2SD/internal]OV-KitKat (JBC based)

What have you got on there??? I used an 8 Gb no issues and even had a linux install on it.

Lots of Pics...quite a bit of music...videos...a few apks that had to be sideloaded because direct downloads wouldn't work...some zip files (games for emulators). Trying to clear out stuff as we speak.

 

[Melvin Jefferson]

Re: [ROM+Kernel][CM-11.0][4.4.2][OS2SD/internal]OV-KitKat (JBC based)

officially, google stopped supporting armv5 as of ics. They never supported armv6 at all... now almost all gapps are built for armv7, d any with thumb2 assembly crash "legacy" s CPUs like ours.
Honstly, I'm surprised that any new gapps run at all since there's basically zero support. The things that still work, google hasn't tried to optimize for speed yet.

Any plans on an update soon Squid? Perhaps 4.4.3?

 

[Toucan4267]

Re: [ROM+Kernel][CM-11.0][4.4.2][OS2SD/internal]OV-KitKat (JBC based)

Any plans on an update soon Squid? Perhaps 4.4.3?

Read post #695...

Sent from my Nexus 7 using AC Forums mobile app

 

[bigsupersquid]

Re: [ROM+Kernel][CM-11.0][4.4.2][OS2SD/internal]OV-KitKat (JBC based)

Any plans on an update soon Squid? Perhaps 4.4.3?

I wish.
I still haven't had a chance to determine what bootloops every build since the last upload.
Suspect selinux has to be enabled. Pretty sure for 4.4.3 with its @!#%?!! Extra Security Features.
May have time later but not soon.

 

[yaconsult]

Re: [ROM+Kernel][CM-11.0][4.4.2][OS2SD/internal]OV-KitKat (JBC based)

I'm trying to install this on my active phone after trying it on on my test phone.
I upgraded my recovery to cwm 6.0.4.5 like I did on the other phone.
Then I took out the sdcard and created a primary fat32 partition followed by a primary ext4 partition of 2 gb.
I copied my rom on the sdcard on the computer, and the plugged it into the phone.
But when I try to choose zip from /storage/sdcard0 I get the error:
E: Can't mount /storage/sdcard0

Am I missing something? Maybe I need to redo the card on my linux system instead of using minitool on windows...

Yeah, that was it - the partitioning was messed up by that mini-tool partition program. Once I did all the patitioning and formatting on linux, it worked as expected. I can not recommend that mini-tool utility.

 

[AndyOpie150]

Re: [ROM+Kernel][CM-11.0][4.4.2][OS2SD/internal]OV-KitKat (JBC based)

I've used it and Gparted and never had a problem with either one. As a matter of fact I just recently used Mini Tool to delete all partitons on my sd card and repartiton with a 1.5GB ext.4 partition. Worked fine.

 

[bigsupersquid]

Re: [ROM+Kernel][CM-11.0][4.4.2][OS2SD/internal]OV-KitKat (JBC based)

just for fun, pulled 4.4.3 and going to try to build.
Low expectations... but who knows without giving it a try.
Kernel source has update too.

 

[bigsupersquid]

Re: [ROM+Kernel][CM-11.0][4.4.2][OS2SD/internal]OV-KitKat (JBC based)

I've used it and Gparted and never had a problem with either one. As a matter of fact I just recently used Mini Tool to delete all partitons on my sd card and repartiton with a 1.5GB ext.4 partition. Worked fine.

I haven't tried window$ to partition since around 2011. I've used gparted mostly, sometimes with the card in a reader but usually just in the phone mounted as external storage either in recovery or an internal ROM.

 

[yaconsult]

Re: [ROM+Kernel][CM-11.0][4.4.2][OS2SD/internal]OV-KitKat (JBC based)

Have others noticed an issue with screen updates in navigation? The screen jumps around a lot and sometimes the same strip of screen is redrawn multiple times. This happens even when the phone is sitting on my desk after being given an address to navigate to. It looks like it's being drawn in a slightly different position every second or two.

I tried it when I went out yesterday and my test phone behaves exactly the same way in navigation with this rom, so it's not a hardware issue.

 

[bigsupersquid]

Re: [ROM+Kernel][CM-11.0][4.4.2][OS2SD/internal]OV-KitKat (JBC based)

Have others noticed an issue with screen updates in navigation? The screen jumps around a lot and sometimes the same strip of screen is redrawn multiple times. This happens even when the phone is sitting on my desk after being given an address to navigate to. It looks like it's being drawn in a slightly different position every second or two.

I tried it when I went out yesterday and my test phone behaves exactly the same way in navigation with this rom, so it's not a hardware issue.

it's a maps issue with the old adreno drivers.
You have to use an older version of maps sideloaded to avoid it. I'll look up which one for you.
I believe it's 1.6 something. Found it on xda for another legacy device a while ago, searched adreno 200 google maps glitches|artifacts or something similar.
1.7 still glitches badly.

oh, I also got less of it with the most current gapps from the pa_gapps xda thread. But they take up a lot of space... needs OS2SD or to wangle them in using Toucan's mount scripts and manual copy/perm setting.

 

[yaconsult]

Re: [ROM+Kernel][CM-11.0][4.4.2][OS2SD/internal]OV-KitKat (JBC based)

Thank you very much, bigsupersquid!

For any others who need it, I located the thread with download link here: [ROM] CM-10.2 | AOSP 4.3.1 Jellybean [KANG] [Oct-31] - xda-developers

And, that version did, indeed, solve the problem. The drawback is needing to turn off auto-update - otherwise it will upgrade to the latest version which doesn't work properly on this phone.

 

[bigsupersquid]

Re: [ROM+Kernel][CM-11.0][4.4.2][OS2SD/internal]OV-KitKat (JBC based)

Thank you very much, bigsupersquid!

For any others who need it, I located the thread with download link here: [ROM] CM-10.2 | AOSP 4.3.1 Jellybean [KANG] [Oct-31] - xda-developers

No problem, like to keep things plugging along.
Really I'm still flabbergasted how much use other people get out of this experiment. It was really just a project for my own use, decided to share like other nice devs do, and now look what it's grown into.

 

[Hugh Johnson]

Re: [ROM+Kernel][CM-11.0][4.4.2]OV-KitKat (JBC based)

I'm not sure what's going on but I can't install either package. I'm using ZenGarden 2.0.3.3-T if that's an issue...?

I've confirmed the MD5 checksums.

Both packages return the following

Finding update package...
Opening update package...
Installing update...
set_metadata_recursive_: some changes failed
E:Error in /sdcard/cm-11-20140315-OS2SD-thunderc-md5-b16da7521d696930fa49a72930b54df7.zip
(Status 7)

Installation aborted.

Install from sdcard complete.

-- Check zip for errors.

Hopefully I can go back to OM-Mandylion-20130112.

Thanks for any help. Glad to see we can still keep this phone going. I'm happy paying $25 a month! :-$

- Hugh

 

[AndyOpie150]

Re: [ROM+Kernel][CM-11.0][4.4.2]OV-KitKat (JBC based)

Hugh:
You need to download and install either the philz recovery (for the internal version) or TechVendetta's recovery (for the external version).
TechVendetta's is here: http://forums.androidcentral.com/op...2sd-internal-kitkat-rom-dev-techvendetta.html

philz is here: https://www.mediafire.com/folder/nfgfef6qpril7/CM11

 

[bigsupersquid]

Re: [ROM+Kernel][CM-11.0][4.4.2][OS2SD/internal]OV-KitKat (JBC based)

just for fun, pulled 4.4.3 and going to try to build.
Low expectations... but who knows without giving it a try.
Kernel source has update too.

still bootlooping. Looking into what is actually running. it gets to dexopt of some system stuff then hangs. Probably killing processes like last time.

 

[bigsupersquid]

4.4.3!!

still bootlooping. Looking into what is actually running. it gets to dexopt of some system stuff then hangs. Probably killing processes like last time.

OMFG, it's just done something natty to the boot.img, I bet I messed something up in the device folders.
Swapping in an older working boot.img brings up full boot with new internal build.
I'll get it working enough to upload something new before too long


oh, and I opened up the archived roms for sharing. Sorry, didn't notice that was requested quite a while ago, my email gets stale.