Here's another recovery you can try.
https://www.mediafire.com/?s8c94941y8kubdd
alright, ill jump on that when i get home.
Here's another recovery you can try.
https://www.mediafire.com/?s8c94941y8kubdd
Compiling snippets of c code to to thumb2 and thumb1 and comparing the output could be helpful. If you could figure out what c constructs generate the particular instruction(s) you're trying to convert you could just compare the output. Ideally it'd be nice to have an 'assembler assembler' that could automatically convert the code. I've been meaning to learn more about the arm arch, I may experiment with this a little too. I'd also like to try to get the kernel up to 3.0.101 where the p500 is.ART may or may not happen. I have to learn more thumb assembly to fix it. My decent class for school this session (the easy one since I did 8088 back in 1991) is x86 assembly. Doesn't apply, but maybe I can get more parallell info from it. There's lots of good info out on the net with minimal searching as well, but not much if any on downconversion of thumb2 to thumb1 code. I found enough to fix a few files but there's still more to go. I'd be impressed with myself if I got that to run.
it's inline assembly that's spazzing the build. your architecture can't handle blah blah... I converted some of the stack issues (because of what registers can't be pushed or can't be popped or can't be either) but it is now onwards to other instructions, and my assembly background is 6502, 6809, and 8088. A little archaic. Research is slow since I'm working on classes and job alonside keeping things repaired/tuned for family around the house. I'm pretty sure it can be tweaked over by slowing it down using extra stack space to hold the oversized data and whatver math to compensate for the v7 capabilities. Spoils the point of inline assembly a bit, but for my purposes I'd rather have it run than run as fast as a newer chip allows.Compiling snippets of c code to to thumb2 and thumb1 and comparing the output could be helpful. If you could figure out what c constructs generate the particular instruction(s) you're trying to convert you could just compare the output. Ideally it'd be nice to have an 'assembler assembler' that could automatically convert the code. I've been meaning to learn more about the arm arch, I may experiment with this a little too. I'd also like to try to get the kernel up to 3.0.101 where the p500 is.
there is no english language file lol where might I find it? I can pull from the old rom
Ill post a screenshot later, its english mixed with something called azerbaycanca...weird...everything is english with gigerish mixed in
edit...I cant read enough of the language to set up screenshot from power menu. So do you per chance have a link to the older build or a way I can set my locale back to en? Build.prop is en_US but os is half english half other.
---------- Post added at 01:54 AM ---------- Previous post was at 12:55 AM ----------
I noticed you edited the frameworks file, could that be the issue? Do I need to decompile and recompile with the correct language? I didnt make a nandroid, pretty dumb but I cant read the phone haha. Any help would be super baller.
Sorry I don't.Ok sorry been awhile I tried the cwm you gave me and I still got a bad installation. Do you have a twrp I can use maybe? I have never used twrp so I wouldn't know what to do
Ok sorry been awhile I tried the cwm you gave me and I still got a bad installation. Do you have a twrp I can use maybe? I have never used twrp so I wouldn't know what to do
Wow, OV was my first smartphone. Can't believe people are still developing for it ! :thumbup:
@skinbark hello, I come from the D710 and we're having trouble getting mms for Virgin Mobile working on our kit Kat builds. It seems like the way virgin mobile handles mms is different and they need to be decoded. As of right now mms comes in as a message of garbled text from the number 9999999999. Did you run into any of these issues on your VM build for the OV?
bigsupersquid made a patch for the Virgin mms in frameworks_opt_telephony. He has another thread at androidcentral
https://github.com/bigsupersquid/
use mine. on ac even skinbark said he had been doing so rather than update his build.Is there a fix for bluetooth yet? I've been using this rom for a while and applaud the devs on their work. But I just can't cope without bluetooth.
Sent from my GT-N5110 using xda app-developers app
Ya the main issue is just generally its a bit slow. I'm not trying to be one of those people who dog the ROM cause devs sibt human but this is just what I have experienced. I know our SOC came out when Moses was around so I'm not expecting miracles. I'm not sure if you guys have more planned or not but its really neat how efficient the phone is on 4.4 and if it was to get faster it'd be amazing.
The keyboard, can you guys adjust the size values? Its microscopic! Hacker's Keyboard fits the bill in the meantime.