yashsingh1/xdaforums huggingface dataset:
[Samsung Mesmerize] add144:
I'll have to second that. Stick with the kernel provided. You'll find plenty of performance with it.
[Samsung Mesmerize] ChromWolf:
Neither my work PC nor my laptop will connect via Odin, so without futzing additionally with that, I had a phone stuck on messed-up-MIUI... So over lunch I took your advice.

Back up and running, so that pretty much means it was indeed either the kernel or the extraneous TB data being restored.

Did a TB restore without anything that could possibly contain TouchWiz settings, all apps are back. This doesn't prove anything in particular of course (with the two possibilities noted above), except that my phone is slightly more usable now. XD

Strictly for troubleshooting purposes/for curiosity's sake, if I were to flash to JT's kernel and not muck with TB anymore, observe the results, and either stick with the change (if it was a TB problem) or flash back to nem2all's kernel (if it was a kernel issue), would I be able to do that just by flashing the kernel, or would I need to reflash MIUI itself (Lagfix has yet to be enabled at this point), and then run through TB again? I figure at least if I can figure out if JT's kernel maybe doesn't work as well as Nem's for this ROM, that's gotta be helpful to someone. Thoughts?

EDIT: A ha! The first post says it includes JT's kernel, which confused me. I had seen BDE say in post #84 of this thread that it was actually nem's kernel. I happened to grab JT's latest voodoo AOSP kernel as of 4/15.

Sooo, which kernel does MIUI v8 actually have then...?

ALSO: Bde, you said you found a working MIUI Weather. I found "MIUI Digital Weather" on the market, but it's just sliiiightly different from your screenshot, and not quite as clean looking. Where did you get yours?
[Samsung Mesmerize] bdemartino:
Here is the MIUI weather app I was using, http://xdaforums.com/showthread.php?t=987521.

As far as kernel goes, this should have the old 3-27 AOSP kernel that JT released, I don't recall packaging a different one with v8 so I think it was just a brain fart in that other post where I mentioned nemesis' kernel (that's just what I've been using :)) So feel free to test out JT's recent one, I tried it the other day and had issues with the home button also (I actually was using their radio and CM6 rom tho, so I can't say it was for sure the kernel.) And no, you don't need to re-flash the ROM when switching kernels. :)
[Samsung Mesmerize] ChromWolf:
I've been kinda hoping for this too, even speakerphone is very quiet compared to where it was on stock/PnP EC10.

That said, I'm not sure I'm very happy with the phone app at all. The stock app lets you engage things like speakerphone without switching out of the numberpad, whereas this phone app seems to focus more on bigger buttons (and yet, at least in my opinion the stock phone app handled things just fine). It doesn't keep the screen awake while it's away from my face, and when it's next to my face and I pull it away, it doesn't come back up; I have to hit the power button and unlock the phone like normal. Is this a behavior of the phone app, or a kernel issue? Would flashing to a different kernel address this? ....Is there a different phone app I could grab from another AOSP ROM to put on here, or is it not as simple as just flashing a ZIP with an APK file in it when it comes to a phone app?
[Samsung Mesmerize] asmith001:
Has anyone with Cellular South experienced any problems with data outside our calling area with MIUI. When I had my Hero, roaming data would sometimes not work outside our region with other roms. I'm going out of town this weekend, just wondering if I should flash back to stock before I go.
[Samsung Mesmerize] bdemartino:
This is an ALPHA, I wouldn't count on it working in odd situations such as that. I would flash back to be safe (make sure you disable lagfix before using odin!).

Just make a nandroid backup, then when you get back from out of town you can re-flash the .zip and then restore your set-up.
[Samsung Mesmerize] asmith001:
I just flashed back to stock with odin after disabling lagfix... I keep getting a vibrating bootloop. Any ideas?

edit: sorry, I got it straight. I had to wipe data from stock recovery. Confusing. Still haven't grasped having both recoveries.
[Samsung Mesmerize] ChromWolf:
I've also found that when I initiate some phone calls, I'm unable to hear the caller, and they are unable to hear me. Hanging up and calling again seems to correct the issue. As much as I hate it, this may actually force me to abandon MIUI... So I'm hoping that maybe tomorrow I can play with a different kernel.

Trouble is, I'm concerned that the various Mes-compatible AOSP kernels out there may just use the same code for the phone driver. Has anyone had issues with MIUI's phone calling, switched to a different kernel, and had better luck? I can try it on my own, but I'm hoping to have some positive results from someone else to convince me I should stick with MIUI, it's so damn pretty. :{

EDIT: ....Sol I'm strongly considering running a Nandroid backup, and then pulling the Phone.APK from either the Vanilla Froyo or CM6 ROMs and flashing it like a mod to MIUI not unlike a PnP mod for TW. ...But is it that simple? Do I just need the folder structure in the ZIP? Is this just plain a horrible idea? ...Will it do me absolutely no good because they all use the same Phone.apk...?

I like the idea of swapping out phone apps, it tricks me into thinking "Hey, I'm a MODDER now!!" (LOL), and I'm okay with borking my phone up as long as I can Odin it back to where it was, but I don't have a problem with people telling me it's a terrible idea. XD
[Samsung Mesmerize] bdemartino:
Can't advise on the phone call issues, my volume was definitely lower than it should be but I didn't make/receive enough calls to notice any issues I guess, or didn't have them. I've been running CM6 for a few weeks now so I'm out of the MIUI loop so to speak. The volume issue needs to be looked at yet as JT has recently found a fix with CM6 and his kernel's.

As for the phone.apk, you could definitely try from another AOSP build but my guess is that it would just FC on you, as MIUI is quite different in a lot of ways from what I understand. It's no big deal to do it, you could swap it into a theme or mod flash.zip (removing the other things of course, and putting it in the right folder structure - but the install script doesn't need any modification so you could flash it after you package it up correctly. Just do this with 7zip, no need to extract the flash.zip.) After testing you can always recover the backup you make.
[Samsung Mesmerize] ChromWolf:
Found settings for forcing the phone to disable the screen with the proximity sensor when the phone app is in use, and I think it's also *maybe* helped with preventing the screen from shutting off after the normal time-out while the phone app is running. I gave it a good long try, I may even kick my screen timeout way down to further test.

So, the only remaining issues I haven't fixed are low volume in calls, and some calls being totally muted for both me and the person on the other end. However, as that could be chalked up to a volume issue as well, I think I'm moving over to maybe a different kernel to fix the issue.

Should I just try out the newest version of JT's AOSP kernel, or has he not yet published the fix he found on CM6's end?

...I like the idea of still messing with the phone app at a later time (assuming a different kernel fixes the volume issue), but I'm not sure I've got any MIUI mods I want to try to hack up. How tricky is it for someone to write up a script for it quick, or point me in the direction of a MIUI mod that I could hack up?
[Samsung Mesmerize] sageDieu:
What did you do to fix the prox sensor issue? I've been annoyed by that.

Sent from my MIUI SCH-i500
[Samsung Mesmerize] ChromWolf:
Least as far as I'm seeing, Settings-->Common Tab-->Call Settings, and I checked both "Enable Proximity Sensor" and "Enforce Proximity Sensor". FWIW, I have yet to experience the "no volume for either party on outbound call" issue since then, but it may just be a fluke, and it wasn't all the time even before.
[Samsung Mesmerize] akellar:
How do you get Swype back on this Rom? Tried Beta and it won't generate a new license (assuming its because its pre-installed originally) and flashing another version results in FC.

Edit - NM apparently a reboot fixes whatever issue it had. Move along.
[Samsung Mesmerize] asmith001:
Does that mean there is no development moving forward with this rom?
[Samsung Mesmerize] bdemartino:
I never developed the ROM to begin with, I (along with the other's who helped out) just made certain edits to get it to work on the mesmerize from the work the fascinate guys had done. There has been mention that they are trying to port over 2.3 MIUI, but no further development with this ROM.
[Samsung Mesmerize] ChromWolf:
In the event anyone was watching my phone problem with similar issues (I know, vain much, right?): Switching to the CM6 port's Phone.apk seemed successful in stopping the "no audio at all on outbound call" issue I was having, but I received a call I was completely unable to answer (phone began ringing but with a ringtone I had not selected, no screen wakeup, manually waking the screen did not reveal the phone app, phone *still* ringing, manually opened dialer, phone STILL ringing and had not sent call to VM, dialed out finally stopped the ringing). I was forced to switch back to Phidelt's Pick-n-Pack ROM for now (it's my only phone, I NEED to be able to take/make phone calls).

With the dwindling activity of this thread, I posted about it in the Fascinate thread in case anyone had actually heard of what was going on for me. Deez himself actually responded (see post here), and mentioned there was a "modified MIUI build that should have the phone fixes in there". I'm not quite sure where the link he was referring to was, but I'm definitely wanting to try it and see if it works for the Mesmerize.

Bde, do you recall hearing about such a modified build, and is it already included in the latest alpha build in the OP? It's almost like it's not active or something, at least for my phone... If I could get this working and in- and outbound calls were 100% reliable, I'd go back to MIUI in a heartbeat (at least MIUI weather seems to work on EC10, sorta)

What say you sir?
[Samsung Mesmerize] akellar:
I have been running version 8 for a little over a week now and haven't experienced any of the issues you have mentioned. The Rom is awesome and I am just crossing my fingers someone can get the update GB version going.
[Samsung Mesmerize] bdemartino:
I kanged his 04/04 release and that is what is packaged up here in v8, i see that he's updated his change log with a 04/06 listing - this one I never did get my hands on and could very well be the fix he's referencing in his post. Will try to find time to port it unless someone else wants to try :P it'll have to be ran on their radio until someone can fix the sms padding issue ever present in the fascinate to mesmerize kang.
[Samsung Mesmerize] bdemartino:
I was in this boat when I was still running it, the only issue I had was lower call volume (even at max setting), that was basically it aside from the original build issues.
[Samsung Mesmerize] ChromWolf:
Could be a fresh re-flash would even do me? Or I could just be screwed and it's just something with my particular hardware.

Deez seems to share at least a brief insight as to where things are headed with the GB port. Click the post link I linked above for his thoughts on the GB port if you're interested.

If I can confirm that it is, I'd LOVE to try, but... I am no dev. I don't know the languages, I am not a programmer, I just have Phi's dev environment set up with Eclipse installed, and that's it. If it's pretty straight-forward and just takes time, just tell me how. Same thing for the SMS padding; seems like it's always swiped from JT for every build.

Like I say, I'm not a dev. I could be saying I'll do something that is so far above my head the ROM will get opened, not attempted at all, and we're stuck waiting for Bde to have the time to do it anyway. But I *do* want to help if I can, and learning Android development would be awesome, and if it keeps one more thing from landing on Bde's plate, that's cool with me. Just fair warning.
[Samsung Mesmerize] bdemartino:
You don't need a dev environment to make said changes, it's actually as easy as decompiling framework.jar (using apktool) and editing a particular .smali file called Bearer.Data (this is written in a java assembly language, which I know nothing about lol) to remove the padding as stated on JT's github commit. I actually haven't been able to do so myself, that is where l3ttuc3 has been a huge help. so I would have him do it then fix up the build.prop and other XML edits (this is still all done after it's built, so no need for dev environment - this was confusing for me at first too, you only need the environment if you're making the changes to the source code rather than after it's already been compiled).

I don't know if his newest release will fix your problems, but it's worth a shot - but the issues could still possibly be unique to your phone :(
[Samsung Mesmerize] ChromWolf:
I wonder if this Bearer.Data could be overwritten with a previously-edited version, say extracted out from the Mes MIUI v8 port? I may hit up L3ttuc3, but I'd like to at least *try* to do it on my own, though I suspect a lot of comparing code with the v8 build will happen. I dunno if you guys also had this, but I may also try to change the black text in the notification window. That may just be a result of the Frois theme I was/am still so anxious to run, so I may need to just worry about that myself.

I did catch that everything except the 4/06 commit were build with both MIUI 1.3.25 and 1.3.11, whereas the 4/06 commit was purely 1.3.11. Who knows, maybe that'll be a good thing in trying to get it to work on my phone? It may also make it harder to just overwrite the code I'm hoping to overwrite. :P I suspect hanging out in the IRC chan is required. gee darn. XD
[Samsung Mesmerize] bdemartino:
This^ :p

I've tried swapping in the Bearer.Data but haven't had luck doing so, so l3ttuc3 has been redoing it each time we get a new one to kang.
[Samsung Mesmerize] ciiara:
So will the In Call Volume be fixed anytime soon? ^_^ Not to sound ungrateful! I love this rom
[Samsung Mesmerize] MrSpradlen:
Looking forward to more updates on this rom, looks awesome. Great work guys!
[Samsung Mesmerize] MrSpradlen:
How are things goin with this?
[Samsung Mesmerize] bdemartino:
Uh, as I tried to state in the original post - I didn't develop the ROM I just took the work the fascinate guys had done and made the proper edit's to get it running on the mesmerize. So unless the fascinate guys get something working or make an update, you won't see any advances with this.

As far as the ever plaguing mms/camera/bt issues with AOSP builds - hopefully someday we may see a fix - but from what I've heard it requires some sources we currently don't have access to. (Either way, the real developers, those who build these things from source, would have to have fixed it before I or anyone else could kang it to the mesmerize.)
[Samsung Mesmerize] ChromWolf:
And really, the Fascinate thread for their MIUI port isn't going anywhere either; most of the developers seem to have moved into Gingerbread ports.

There's a silver lining to that dark cloud though; the latest release of official MIUI is Gingerbread based. I personally would LOVE to see a Gingerbread MIUI for the Mes (and by virtue, the Fascinate, etc.), and would love even more to be involved in building it; and as far as "being the first", I don't think anyone else is really working on it, I think everyone's mostly focused on CM7..... But I am no where even close to a developer. I'm not even worthy of saying I've kanged a ROM after it's been compiled.

But I'm learning. I'm beginning to research the fundamentals of kernels and scripting, and I hear advanced developer terms thrown out in IRC, but I don't fully know what they mean.

The bottom line is this: I want GB MIUI. I want it to work 100%, but I'll be happy if call volume was adjustable. I can't do it right now; I don't know how, and someone else may do it before me by the time I *do* learn how. I'm not making anything even close to a promise, and you shouldn't hold your breath. But I love using MIUI, and I want it up and running. If I actually get somewhere with it, XDA will be the first to know. Well, second. The IRC chan will be first. XD
[Samsung Mesmerize] bdemartino:
Honestly from what I've learned over the past few months, this is how most of these developers have become... developers. Even people with vast experience in coding languages still have issues learning how to develop android. The only way to learn is to dig in, look at the code, and research research research. (mostly by just asking the other guys who have had experience working with it already) So keep at it! jt1134, adrynaline, phidelt82, nemesis2all etc. are all more than helpful when it comes to questions and pointers, so pick up as much as you can from those guys (and anyone else of course) as you run into any road blocks.

As for a GB MIUI, I'd like to see it as well - however - at this point the issues plaguing the AOSP builds will still be present in a 2.3 port of MIUI because the base that must be used is AOSP/CM7 (as far as I know). So at this time, I don't see a fully functional MIUI build as being possible regardless of version (2.2 or 2.3.) until the base ROM is fully functional (which from what I've heard requires some sources we do not have).
[Samsung Mesmerize] ChromWolf:
I'm gonna use this as my opportunity to call out to the community and say if you want MIUI as well, and wanted it updated, here's your chance to help with it. I think if enough people decide that saying "when will it be done" isn't as good as saying "how can I help", we cane go somewhere. That's not calling anyone on the carpet; that's just saying, consider jumping to the next step. Sort of an "Ask not what your developers can do for you..." kinda thing. :)

I'm most definitely not holding my breath on MIUI GB; I'd LOVE to just be good enough to port over pure MIUI to the Mes, but I'm no where near that good, and not even the devs BDE listed above are doing that for the most part (jt may be the exception). I'd love to find a mostly-similar device hardware wise that has an active MIUI port (as in, from the MIUI Dev site), but that's also CDMA; and that's been one roadblock.

I'm cool with just slapping in the CM7 parts, but for one, it seems "quick and dirty", which doesn't seem fitting with the concept of MIUI, and for another, I dislike the idea of being stuck with the same issues as everyone else's AOSP builds; it just feel like I'm stuck relying on those devs to fix them. And maybe that's true; like I say, I'm no dev, and these guys totally are, and I may be stuck dumping CM7 parts into MIUI to get it to work. I just can't in good conscience go about it without trying it my way first, just to see what happens. XD

I'm kinda thinking "aloud" here, so I'll wrap this up.
[Samsung Mesmerize] bdemartino:
If your main goal here is to get a fully functioning MIUI (or any AOSP for that matter) then i would say you would need to focus on the AOSP rom- jt1134 has a great github and it's well organized so that others are able to use it (he has a tree for AOSP) - lmartin92 was able to sync his repo and make the proper USCC edits and then build the native mesmerize ROM from it- I'm not sure if lmartin's github is up to speed and able to be used by outsiders but you may try contacting him. He's currently working on a native build of CM7 through the same process (using jt's source once again) last I heard.

Once you were able to have a full build done and booting, then you would be able to test and troubleshoot on the phone(using logcats, don't forget that the radio has a different logcat, can't remember the commands off top) then go back to the source code to determine the fix. This appears to be how punk.kaos has been going about fixing up the camera in his CM7 build (from what I've read on his twitter) but I may be missing a step or two in there.

As far as I know, the code within the source is mostly C++ vs. what we see post-build (java bytecode, assembly) but I'm sure there are other languages used there too (i've never actually gotten as far as to see what source files look like personally)

That's about the only suggestion I can think of for a starting point at this moment.
[Samsung Mesmerize] ChromWolf:
I'm gonna go ahead and put this out there in hopes the right people are watching.

I've been kinda keeping it under wraps since I honestly don't know what the hell I'm doing as I've never done it before, but... I'm VERY SLOWLY working towards porting GB MIUI. I finally caught a bit of a break with the scripting, and got it to flash yesterday evening.

Don't get your hopes up just yet; pretty much NOTHING worked. In fact, the only things that *did* work were the launcher screen (could drag the screen back and forth), and the already-included CM7 "TV shut-off" animation when you turn the screen off. EVERYthing else is pretty much broken. I don't even know if call volume will be adjustable in this ROM, since this experiment was using the Nexus S (which is GSM), so the radio is completely broken. I knew it would be, but still.

I REALLY want GB MIUI, but I'm starting to get to the point where I think I'm in over my head, and could really use some help. If you've ported ROMs and miss having an up-to-date MIUI, here's your chance to get in on it.
[Samsung Mesmerize] sageDieu:
*hug*

I'm nowhere near being able to help develop but would love to test if you get there. I'm sure you can find some interested developers, probably bde, dfgas, lmartin, etc... good luck.

Sent from my CM7 SCH-i500
[myTouch 3G, Magic General] gotgohan:
I am sorry for making multiple threads, I am so lost, I was asking the wrong questions.

This is my phones information when I did 'power down + power on'

SAPPHIRE PVT 32A SHIP S-ON G

HBOOT- 1.33.0013 (SAPH31000)

CPLD-13

RADIO2.22.28.25

OCT 21 2009,22:33:27

HBOOT

<BACK> FastBoot Mode

Can I just flash any Hard SPL I want without worry?
[myTouch 3G, Magic General] tvall:
No. the only spl that works fully on that phone is 0013 or 0013d
[myTouch 3G, Magic General] mumilover:
Well... you can flash the 1.33.2010 eng spl to do some stuff. But if you want a fully functional device, you have to flash the 0013 or 0013d spl as tvall stated.
[myTouch 3G, Magic General] gotgohan:
So I just download 0013 or 0013d spl and just flash it in recovery correct?

Then I will have a better recovery, thus making it easier to install radios, and maybe even Rom's?
[myTouch 3G, Magic General] mumilover:
no.... you must need an eng spl... the 1.33.2010 or something.
[myTouch 3G, Magic General] tvall:
The 0013 and 0013d radios are almost exactly the same. to flash roms download rom manager from the market. Them use that to get clockworkmod recovery. You flash roms from that
[myTouch 3G, Magic General] gotgohan:
Here are my questions now:

Can I install Radio with Rom Manager?

Can I install SPL with Rom Manager?

If not, I read this: http://xdaforums.com/showthread.php?t=605239. How do I do a full backup with nandroid or w/e it is.

As I think I know what it means, this is what I did:

I installed that app 'Rom Manager, then installed clockword' but when I did it the first time I clicked the 32B one on accident first, so I redid it with 32a one. It gave me the option of the 2. Now when I tried to make a backup with the app, it would restart, and just sit at the mytouhc screen =( I messed up? The phone still works, I just had to pull battery.

I even tried using RA 1.7 from the ROM manager and it still sits at green screen if I boot in recovery =/