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

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

Apps I like: audible, camera zoom fx, catan, dolphin browser, elixir widgets, quickoffice, Swype keyboard, osmand, Pandora, weather channel, appgratis, avast, es file explorer, Google search, mx player, mysword, pitchlab. That's a start anyway. ;-)

Sent from my Nexus 7 using AC Forums mobile app
 
Re: [ROM+Kernel][CM-11.0][4.4.4][OS2SD/internal]bigsuperROM-thunderc-4.4.4

My wife just informed that she had just ordered me the Dalaxy S3. With me being partially blind, a bigger screen would help. I"m definitely keeping mu OV on hand though to play with your builds. I shudder at the thought of having to start all over again on a new phons though.

Sent from my ZombieKat 4.4.4-VM670 using Xparent Skyblue Tapatalk 2
 
Re: [ROM+Kernel][CM-11.0][4.4.4][OS2SD/internal]bigsuperROM-thunderc-4.4.4

My wife just informed that she had just ordered me the Dalaxy S3. With me being partially blind, a bigger screen would help. I"m definitely keeping mu OV on hand though to play with your builds. I shudder at the thought of having to start all over again on a new phons though.

Sent from my ZombieKat 4.4.4-VM670 using Xparent Skyblue Tapatalk 2
Never has there been a community like the Optimus V/S. ;)

I miss the old days when I first learned how to flash, lol. :p
 
Re: [ROM+Kernel][CM-11.0][4.4.4][OS2SD/internal]bigsuperROM-thunderc-4.4.4

Never has there been a community like the Optimus V/S. ;)

I miss the old days when I first learned how to flash, lol. :p

The better half got a phone a year ago and all they've managed to do so far with it in a year is root it and flash a fresh copy of the stock rom. If I've learned anything it's to grab a phone that's just a tiny bit dated just to make sure it has some form of development going on, because it's roms like these that make the V so relevant and fun to have years after it's been released
 
Re: [ROM+Kernel][CM-11.0][4.4.4][OS2SD/internal]bigsuperROM-thunderc-4.4.4

One nice thing with the S3 is that there"s tons of ROMs to play with. Although, i"ve already picked my ROM. Whenn it comes, i'm going with PacROM. At lea

Sent from my ZombieKat 4.4.4-VM670 using Xparent Skyblue Tapatalk 2
 
Re: [ROM+Kernel][CM-11.0][4.4.4][OS2SD/internal]bigsuperROM-thunderc-4.4.4

Well, we'll just see how this flies.
androidarmv6 made some fairly major tweaks.

it'll require changing the recovery... again for you all, but for the first time in a while on the p500.
enabled tls (thread local storage,) and they reversed the system and data mtd partitions in the kernel!
which means, for you folks on zvj baseband, your /system size problems will just... go away.
for optimus V, that's 190MB total for /system, vs the 167MB it's got now.
and maybe I can put the file manager and terminal back into the internal build.
but, it'll invalidate older /data backups that're bigger than your old system partition size..

assuming it builds and flashes and runs ok, that is.
 
Re: [ROM+Kernel][CM-11.0][4.4.4][OS2SD/internal]bigsuperROM-thunderc-4.4.4

well, it does work.
benchmark is nice. vellamo says linpack of 14.71 mflops which compares to pre-linaro os2sd.
I show /system size of 179MB with nothing but the base install.

I now have logs of the broken camera, so don't need them anymore.

I didn't miss CWM at all, and TWRP needs patched for the TLS kernel so won't boot yet.
androidarmv6 has CWM looking much nicer than the last time I saw it, though. The animations work, and the text is smaller and looks sharper.
have to fix the camera and finish poking at accelerometer before releasing.
 
Re: [ROM+Kernel][CM-11.0][4.4.4][OS2SD/internal]bigsuperROM-thunderc-4.4.4

Okay!! Game-wise:
For Gameboy, I'm running Gameboid myself. It seems fairly okay - bear in mind that I'm using an Optimus S on ZVD with this ROM - but most games that have complex motions involving the d-pad & buttons (usually fighting games & platformers) won't work so well. Other games (like Summon Night: Swordcraft Story and Rockman EXE/Megaman Battle Network) where you can run around are a bit of a pain because the directions tend to get mixed up when running. A lot. And some games just plain won't work - the GBA port of Zelda 1 (Famicom Mini Zelda no Densetsu 1/NES Classics The Legend of Zelda) simply refuses to load, and Final Fantasy V Advance gets about halfway through the first story sequence (after selecting New Game) before "resetting itself" (the game, not the device).

For other emulating goodies, I had been running John NES, which was okay. But then I got my mitts on Nesoid, tried it with Zelda 1 (yes, I have the roms for the Nes & GBA versions, lol...just sayin'), and *immediately* got rid of John NES. It's immensely superior...picture is larger, the games run faster. Except neither emulator liked Castlevania very much, controls were just a pain in the shell. So once again, it's down to simplistic stuff that doesn't take complex motions (like Zelda & Final Fantasy).

With apps & games...um...yeah, that Toucanscrypt is awesome for getting stuff in there!! Just be warned that there are some that you could either download from Play Store OR get online and sideload...and they just won't work, whether they're compatible (according to Play Store) or not. (Examples: Angry Birds Epic, Eternity Hero, King of Fighters 97, Shin Samurai Spirits/Samurai Shodown II; these ALL force close immediately) That said, some awesome stuff would be: Sonic 1 (the Android version blows previous mobile versions away mainly because you have the Spin Dash from later games as an option, and you can unlock the ability to play as Tails and/or Knuckles), Sonic 2, Sonic 4 ep1 (you may have to actually pay for Sonic 4 ep2, as every site I downloaded the apk from would cause the sideloaded apk to fc immediately), Bloody Alice Defense (this game is tough but addictive), and whatever else floats your boat.
As for how they run, well...Sonic & Angry Birds all run pretty smoothly for me. Angry Birds Star Wars 2 has some slowdowns, but my ex's Galaxy S4 *and* LG Optimus Exceed2 both experienced that with ABSW2, so that may be a thing with the game itself. My RPGs are pretty smooth sailing, except for Zenonia 4, which is fraught with slowdown (this may be a thing with the game as well, it runs barely faster on my Galaxy Rush and it still ain't all that smooth or fast on my ex's Optimus Exceed2).

Also, with the 4.4.4 KitKat update still barely rolling around officially, there's quite a few apps that don't have support for this yet. (ex.: MX Player won't work anymore, it says "Unsupported Android Version" and force closes. However, on older 4.4.2 versions of this ROM, it worked just fine. Oh well...I can wait. :) )

Let's see...the clock lag while connected to Wi-Fi seems to have finally stopped happening (it has me a bit paranoid, though - I'm constantly checking it), and the battery drain isn't *too* bad anymore, either. All in all, I'd say it's going quite swell now. Just need a new SD card.
 
Re: [ROM+Kernel][CM-11.0][4.4.4][OS2SD/internal]bigsuperROM-thunderc-4.4.4

ok, got working twrp and cwm for latest wacko version now.
this next release, when I get it out there, invalidates flashing old kernels, or the new kernels over old roms.
it reverses /data and /system on internal build to open more space, for something like up-to-date 4.4.4 gapps not sideloaded to /data.
it turns on hardware tls (thread-local storage) for yet more speed (it's been emulated in the kernel up till now apparently)
requires new recovery yet again. because of the mtd partition swap in the kernel, mostly.

if you all could post me the size of your /data partitions before linking them that would be helpful.
that info is in settings>about phone>partition info
or adb shell busybox df
 
Re: [ROM+Kernel][CM-11.0][4.4.4][OS2SD/internal]bigsuperROM-thunderc-4.4.4

My Optimus S has a /data partition of 165MB.

Sent from my SPH-M830 using AC Forums mobile app
 
Re: [ROM+Kernel][CM-11.0][4.4.4][OS2SD/internal]bigsuperROM-thunderc-4.4.4

/data
226MB/0.94GB

Optimus V VM670 Virgin Mobile


edit,

Oops, you were asking about internal builds. Damn it, sorry about that.
 
Last edited:
Re: [ROM+Kernel][CM-11.0][4.4.4][OS2SD/internal]bigsuperROM-thunderc-4.4.4

OMFG, if you'll forgive the teen-speak.

Androidarmv6 fixed and enabled ART for armv6. I saw it here first, thank xu3sno for pointing it out. I might've missed the information.

Not only will that make kitkat more fun to play with, it makes L feasible on the V. which otherwise would've probably been highly unlikely.

aw, dang it, now I'm going to have to make another build and release it before too many more days go by or this is just a horrible tease. The TLS and mtd swap were bad enough to dangle out there without a build.
 
Re: [ROM+Kernel][CM-11.0][4.4.4][OS2SD/internal]bigsuperROM-thunderc-4.4.4

Not sure if you still need it, but my Optimus S ZVJ has 165mb for /data. Will be switching to os2sd once next build is released (patiently waiting; no pressure).

Just to make sure: the os2sd build link system files to SD, while toucanscrypt link app files to SD. Is this correct? And is os2sd build still a bit slower than internal? Sorry am a bit slow myself.


p.s. Just learned how to use thanks on this board. Get ready for spam in your inboxes gents.
 
Re: [ROM+Kernel][CM-11.0][4.4.4][OS2SD/internal]bigsuperROM-thunderc-4.4.4

the os2sd is actually noticeably faster than internal with a decent sd card.

os2sd doesn't link anything... it actually mounts the 3rd and 4th external sd partitions as system and data instead of mounting the internal partitions.
toucanscrypt links system and data stuff to the sdcard 2nd partition.

from the /data sizes posted the optimus S is all around smaller inside than the V. Boo. on ZVD/ZVJ, data is slightly smaller than optimus V zv4 system partition. the mtd swap will allow optimus V sized builds on the S but no extra room beyond that. the V is just bigger... but I'll keep building for the lowest common denominator.
at least 165MB is enough for 4.4.4 internal gapps without having to put up-to-date gms and vending on /data.

and one of these days I'll have to mess with the automated aroma maker.
 
Re: [ROM+Kernel][CM-11.0][4.4.4][OS2SD/internal]bigsuperROM-thunderc-4.4.4

well, I am finally satisfied with the accelerometer/compass.

the two thunderc ami304d binary blobs (froyo and gingerbread) both jittered really badly in google skymap and threw repetitive logcat errors, plus they had that nasty sleep/calibration loop issue.

the thunderg blob had output smooth as butter in the skymap, and didn't throw any errors or have sleep issues. but the skymap was like looking in an inside-out mirror. I figured out the magnetic x and y were both negative (flipped around their respective axes.) I suspect the ami chip is mounted backwards or something in the thunderc.

I tried and tried to fight the thunderc blobs into working without jitter, but always at north and especially south they were horrid. (they do jitter a bit in mirage, even, in the skymap compared to my evo.)

I gave up on the thunderc blobs and decided to invert the kernel output to the closed-source middleware thunderg blob instead.
So I dug until I found a likely spot in the ami304.c driver, grabbed debug output code for the mag sensor
Code:
	if (AMI304_DEBUG_DEV_STATUS & ami304_debug_mask) {
		int mx, my, mz;
		mx = my = mz = 0;

		mx = (int)(databuf[0] | (databuf[1] << 8));
		my = (int)(databuf[2] | (databuf[3] << 8));
		mz = (int)(databuf[4] | (databuf[5] << 8));

		if (mx>32768)  mx = mx-65536;
		if (my>32768)  my = my-65536;
		if (mz>32768)  mz = mz-65536;

		AMID("Magnetic Raw Data: X=%d, Y=%d, Z=%d\n", mx, my, mz);
	}
and modified it to read the 16-bit (two-byte each) mag x and y outputs, negate the translated results, and translate those back to two single bytes before writing the buffer to the kernel output.
Code:
// invert mx and my for thunderc to use better resolving thunderg ami304d blob
		int mx, my;
		mx = my = 0;
		mx = (int)(databuf[0] | (databuf[1] << 8));
		my = (int)(databuf[2] | (databuf[3] << 8));
		if (mx>32768)  mx = mx-65536;
		if (my>32768)  my = my-65536;
		mx=-mx;
		my=-my;
		if (mx<0) mx=mx+65536;
		if (my<0) my=my+65536;
		databuf[0]=(mx&255);
		databuf[1]=(mx>>8);
		databuf[2]=(my&255);
		databuf[3]=(my>>8);
in front of the line that outputs the buffer it read from the chip to the middleware...
Code:
	sprintf(buf, "%02x %02x %02x %02x %02x %02x", 
			(databuf[0]), (databuf[1]), (databuf[2]), 
			(databuf[3]), (databuf[4]), (databuf[5]));
now the skymap looks just like my evo, except the evo actually jitters more than the V :p
and my old 8-bit assembly programming gimmicks got put to use with the & | << >> (AND OR shift left shift right) binary operators :cool:
and, the most fun part, I shimmed one of those stupid closed-source binary blobs into working right.

I'm posting this code for other searchers in case someone is trying to find a method for inverting the mag outputs on an ami304 driver.

oh, and I'm double-posting it in the ROM and kernel threads both since it does apply to both.
 
Re: [ROM+Kernel][CM-11.0][4.4.4][OS2SD/internal]bigsuperROM-thunderc-4.4.4

the info I got about art was incomplete.
they're still working on it and it won't build yet.
ah well.

but, on the interesting side...
there's now a p500 cm11 using os2sd, which is cool.
 
Re: [ROM+Kernel][CM-11.0][4.4.4][OS2SD/internal]bigsuperROM-thunderc-4.4.4

the info I got about art was incomplete.
they're still working on it and it won't build yet.
ah well.

but, on the interesting side...
there's now a p500 cm11 using os2sd, which is cool.

woah, do you know if that p500 rom will work on the opV? Or is it only for tmobile, etc.. variants?
 
Re: [ROM+Kernel][CM-11.0][4.4.4][OS2SD/internal]bigsuperROM-thunderc-4.4.4

woah, do you know if that p500 rom will work on the opV? Or is it only for tmobile, etc.. variants?

youd have to swap the kernel and several of the other binaries, the fstab, the init.*.rc files...
if you'd like to try it and see what does work, you'd have to modify the updater-script to allow it to flash to the wrong device, with the wrong partition layout to match mine for os2sd, and the flash my os2sd boot.img over it.
big hassle and I doubt it'd work very well.
I just thought it was cool seeing another device using os2sd.
 
Re: [ROM+Kernel][CM-11.0][4.4.4][OS2SD/internal]bigsuperROM-thunderc-4.4.4

youd have to swap the kernel and several of the other binaries, the fstab, the init.*.rc files...
if you'd like to try it and see what does work, you'd have to modify the updater-script to allow it to flash to the wrong device, with the wrong partition layout to match mine for os2sd, and the flash my os2sd boot.img over it.
big hassle and I doubt it'd work very well.
I just thought it was cool seeing another device using os2sd.

I see. I was curious because their instructions seemed very easy to follow. I've been meaning to try out kitkat but the opV forums aren't the easiest to follow. And also their rom has mms.
 

Trending Posts

Forum statistics

Threads
954,354
Messages
6,961,411
Members
3,163,002
Latest member
KimsJain