yashsingh1/xdaforums huggingface dataset:
[Epic 4G Android Development] RandomKing:
The bluetooth boggles my mind, I've been wondering if it's related to whatever plagues the wifi/4G.

As for 3.4.0/3.4.1, if you got one to work, then you don't need the other. Both incrementally update to the same version, so if you've run one, running it again will do a backup/restore install. Unfortunately, this is a biiiit of an experiment and it seems to be going pretty well. Detailed directions, and possibly my own video, will be provided for 4.0.

For example, if you're on 3.3, and you want to clean install to 3.4:

1. Wipe and install 3.4, but this will still perform an incremental.

2. Wipe and install 3.4 a second time, now it will perform a full install.

It's a powerful installer, but I'll need to lay out scenarios. Unfortunately, romgeeks has crapped out and won't let me in. As such, I am in the process of creating a new website. I hope to further improve the modding experience.

UPDATE: Website mostly ported here. Changes coming soon.
[Epic 4G Android Development] siirus09:
Went from Legendary 2.1 MTD to Thunderhawk 3.4.1 MTD with no clean wipe (I'm a rebel), worked perfectly other than not installing a kernel (so it stayed on Samurai seppuku which is fine with me). Should I update to 3.4.2 when its out or are the bug fixes just for the installer script?
[Epic 4G Android Development] RandomKing:
Unless I can confirm a fix on the wifi/4g, then no, no need to update.
[Epic 4G Android Development] DaveWW00:
RandomKing here is my update scenario you were asking people to post:

Updated on ext4 from 3.3 to 3.4. Wiped caches and installed. Installed fine and works great except the 4g/wifi issue persists. I have occasionally had the bluetooth issue also-like the 4g/wifi a reboot fixes it.

If there is anything i can do (send a log file or something?) to help you resolve the 4g/wifi issue let me know. If you can fix that issue this rom would be absolutely perfect in my opinion.

Thanks!
[Epic 4G Android Development] lilajrestnom:
well it already only had 5 msgs in it but i deleted 4 of them just to make sure lol
[Epic 4G Android Development] RandomKing:
Using fresh new files in EL30, I believe, and my testers believe, that the issue will not persist in 4.0.

As for the install, glad to know it's working on both MTD and BML. Thanks.
[Epic 4G Android Development] jeffro18:
As you know I have not been able to make 4g fail after wifi since the test build of 3.4. The official release of 3.4 is quite different than the test build was, but 4.0 alpha has still not failed for me either.

I can see how I didn't notice the new install scripting not installing a kernel as I was always running the same kernel you tried to package with each respective rom prior to flashing. Nothing seemed out of the ordinary untill trying to flash after cm9 in cwm 5.5.0.4.
[Epic 4G Android Development] RandomKing:
Issues Resolved

So it turns out MTD is far more frustrating to install with than previously assumed. And attempting to merge BML and MTD into one fully-functioning installer just caused mayhem.

Kernels weren't installing.

Backups weren't working on MTD.

Several other issues.

BUT I believe I've gotten all of it to work now. I will be posting 3.4.2. This version will be for everyone unlike the last patch. If your phone is on 3.3, 3.4.0, or 3.4.1, then this patch will be for you. I am building in what I believe is the fix to the wifi/4G issue. No promises, I can't personally test it.

This should be the final debugging for my ultimate installer. If everything goes as planned, I'll be dropping the update tonight or tomorrow.

For those of you waiting for EL30, ThunderHawk 4.0 will come capable to update 3.3, 3.4, 3.4.1, and 3.4.2. A one time thing, most versions after 4.0 will only incrementally update the previous version, for simplicity's sake. Otherwise, a backup/restore update will enact instead.
[Epic 4G Android Development] JeffATL:
My phone app just crashed again while trying to switch to bluetooth midcall. I have 0 messages in the "reject with messages" call settings.
[Epic 4G Android Development] jeffro18:
The lady's phone has been having intermittent fc issues with the dialer since updating her from 3.3 manually converted mtd setup to 3.4 official. 4.0 alpha has been solid for me with shadow el30 mtd v3.0. I'm going to put her on that shortly. I would imagine the 4.0 official release will have lots of changes, but she want's her call stability back now lol.
[Epic 4G Android Development] RandomKing:
Odd, I'm running the exact same setup as her with no phone issues.

-Sent from my Random Epic.
[Epic 4G Android Development] jeffro18:
Yeah, it's weird. It took her like 15 tries to call the doctor for one of my daughters today. That's why she was a little upset. Usually she is a good sport about stuff like that. I have not seen it fail, but she showed me her call log from earlier with all of the failed attempts. I'm about due to start her off clean though as she has a few other minor issues that have been persisting for a while that I know are not due to your work.
[Epic 4G Android Development] DaveWW00:
I've been having random dialer issues also. I'm on 3.4.1 on ext4. Get force closes after ending a call (com.process.android.phone I think it said). When i click close it completely locks up the phone and i have to pull battery.

Also sometimes when i try to call someone I have had to try multiple times before it actually dialed and connected.
[Epic 4G Android Development] JeffATL:
Is the 4.0 link still not public?

Any chance I can be pm'd a link ;) (at my own risk of course)
[Epic 4G Android Development] RandomKing:
I set back to finishing 3.4 (and I think I have!). The 4.0 Jeff is talking about is a mostly stock test of the incremental install from EI22 to EL30. It's a much bigger upgrade than from 3.3 to 3.4. Trust me, you'd be downgrading if you used it as is, be patient. Good things come to those who wait. :D

Was this an update or a clean install?

This actually sounds more like the issue with bluetooth itself rather than the phone... which, as of today, I believe I have solved!

3.4.2 coming soon. Should be the final EI22 version.
[Epic 4G Android Development] jeffro18:
Like random said, the 4.0 build I have been using is a highly unthemed build. I only report on it publicly to show random comparisons between my setup and the other phone in my household. I'm playing with cm9 alpha 2 today, but am looking forward to the fully themed 4.0. It's still my favorite setup when i want outstanding battery life and overall needed functionality. The 3.4 release was helpful targeting issues that us few testers didn't catch with the new installer scripting. We can only test so many potential variables between our normal lives and busy schedules lately.
[Epic 4G Android Development] RandomKing:
Ain't that the truth. Most of what I've done in the last 3 weeks is on my lunch break. :D
[Epic 4G Android Development] DaveWW00:
I updated from 3.3 to 3.4

From 3.4 to 3.4.1, I did not wipe the data but it wiped it itself during the install- not sure if that would be considered an update or a clean install.
[Epic 4G Android Development] RandomKing:
Eh, I should have been more clear, but anyone on 3.4 did not need to flash 3.4.1. Both contained the same build number, so one cannot incrementally patch the other. I have, however just uploaded 3.4.2 which WILL patch 3.3, 3.4, and 3.4.1.

Flash this, it contains my attempted fix. So far bluetooth is hanging in there where it previously hadn't, and I suspect/hope I've repaired the 4G/Wifi issue as well.

It will also successfully backup/restore MTD setups now, and a clean installation will install a kernel now as well as a few other things I patched here and there. Should be relatively flawless now.

Thank you again, everyone, for bearing with me through these trials. 4.0 should come along smoothly thanks to experience gained here.

EDIT: Also, this is my new website, I'm abandoning romgeeks. Also seems easier to navigate on mobile. And all uploads are being moved to minus from now on.
[Epic 4G Android Development] locomariachi:
Well I tried to flash, and I'm stuck in a big time boot loop. I was on 3.4 wanted to flash to 3.4.2 and now i have a boot loop that's not letting me do anything. So what should I do?
[Epic 4G Android Development] RandomKing:
Are you on MTD, EXT4, or RFS?

-I have tested this many times on MTD.

And did you have some sort of backup?

-I always recommend backing up before making major changes.

Were there any errors?

-There is a log file on your SD card, please attach that?

Can you flash again?

-It should attempt to preserve data and reflash the phone.
[Epic 4G Android Development] locomariachi:
I'm on EXT4, I do have a backup, i can't see mount my SD-card right now, so I'll have to use someone's phone to put the thunderhawk 3.4 back on my phone and try to flash again.
[Epic 4G Android Development] turkaloo:
Mine is looping too from 3.4.1 to 3.4.2. Had to pull battery. I then wiped cache and dalvic cache and tried again with same results.
[Epic 4G Android Development] locomariachi:
This is my randomlog.txt file

#PARTITION MAP/FILESYSTEM PROPERTIES

pm=bml

sysfs=ext4

syspmfs=bml-ext4

datfs=ext4

datpmfs=bml-ext4

chefs=ext4

chepmfs=bml-ext4

stat=ok

#READING CONFIGURATIONS

lite.version=no

adv.power=yes

scroll.toggles=yes#RESTORE UTILITY

restore failed
[Epic 4G Android Development] RandomKing:
EXT4 as well?
[Epic 4G Android Development] turkaloo:
Yes, I am EXT4 as well
[Epic 4G Android Development] RandomKing:
Damn. It didn't mount a second time, it didn't backup, and obviously restore failed.

Damn damn damn.

EDIT: No wait, that's how it should look. So it did mount properly... where did it go wrong...
[Epic 4G Android Development] locomariachi:
@RandomKing should I just convert to MTD and then go from there or what do you think? I was going to hit up 3.3 for right now then i guess
[Epic 4G Android Development] RandomKing:
Well I do recommend MTD. The space is well worth it and I've had no side-effects. But I will try and sort this out.

To MTD users, the link is still up and should work for you.

Sorry BML users, I'll try and figure this out.

EDIT: Out of curiosity, is it bootlooping on the android animation? Can you flash a kernel?
[Epic 4G Android Development] VassagoX:
If I understand correctly, to get MTD, all you have to do is flash another rom that's on MTD? Are there specific roms that work best with the correct CWM needed?
[Epic 4G Android Development] turkaloo:
Mine never made it off of the first Samsung screen. It flashed there quickly then started over again. I have restored my backup so all is good.
[Epic 4G Android Development] locomariachi:
It gets to just the SAMSUNG part of the boot, then goes into the loop. I can probably flash a kernel. what you got for me?
[Epic 4G Android Development] RandomKing:
Willing to try another for me?
[Epic 4G Android Development] turkaloo:
Yep, I will try another anytime.
[Epic 4G Android Development] RandomKing:
Uploading, I'll send the link to you. This is the simplest fix I can think of without reflashing my phone to BML and testing personally. If it doesn't work, I'll have to fix it later when I get home. :rolleyes:
[Epic 4G Android Development] locomariachi:
I'm game! I was just gonna convert to MTD anyway but I'll try something

---------- Post added at 01:10 PM ---------- Previous post was at 12:54 PM ----------

Weird I installed 3.41 without any problems, so I'm on that one right now restoring my backup
[Epic 4G Android Development] v8bait:
Went from CleanGB EI22 (BML) to the 3.4.2 clearing data/cache etc and hit the boot loop. It goes from the samsung screen to a quick flash of the CWM screen, then back to samsung repeatedly. Flashing 3.4.1 worked, and it came out with Shadow kernel 1.0.6 so it must have pushed a kernel with either the 3.4.2 attempt or the 3.4.1 (which I thought wasn't pushing kernels...)

I'll try flashing another kernel real quick if I can get it to bootloop again using 3.4.2

*results* while on 3.4.1 with shadow kernel 1.0.6 I flashed cleangb kernel and made sure thunderhawk liked it, it did. I then updated to 3.4.2, hit the boot loop, and flashed the cleangb kernel. Fixed the bootloop, booted normal. Wonder how toad's kernel works here anyway, I think I'll stay a while :-)
[Epic 4G Android Development] kehlan:
What's with the "OUT OF ORDER" thing?

I downloaded 3.4.2 earlier and was LITERALLY JUST about to install it, then saw this thread had been updated.

What gives? Was I about to brick my phone?
[Epic 4G Android Development] RandomKing:
No bricking. But BML users will have to restore after it fails. MTD users should have no problem.

-Sent from my Random Epic.
[Epic 4G Android Development] kehlan:
Thanks for the heads up. I believe I'm on MTD, so I should be fine.
[Epic 4G Android Development] RandomKing:
Nvm. I wonder if this is an incompatibility of the EL30 phone.apk with EI22?

On the other hand, I think I know what's wrong with the BML installation... ill try and fix it tonight.

-Sent from my Random Epic.
[Epic 4G Android Development] JeffATL:
I just want to clarify that this error happened on 3.4.0, I have not flashed to 3.4.2 yet.

(not sure if its relevent but I have the EL30 modem installed)
[Epic 4G Android Development] kehlan:
Does the 9-Lock Mod work on 3.4.2? I'm getting installation error in CWM when I try to flash the .zip...

EDIT:

I'm noticing that the latest upload of the 9-Lock theme has a right bracket ("]") at the end of it.

I'm assuming it was slapped accidentally whilst naming the upload, so I figured I'd call it out and suggest a rename. It adds "%5D" to the end of the filename upon downloading. Just a heads up.
[Epic 4G Android Development] xjayman:
I installed mtd version...running nice
[Epic 4G Android Development] kehlan:
Mine is, too. I just really wished I could get the 9-Lock mod installed -___-
[Epic 4G Android Development] jeffro18:
I don't think he updated the 9 lock mod scripting to install on mtd. You can try mounting system first, but it probably won't work. The same think happened with the lite/full switcher untill he updated it. I doubt he planned on updating the 9 lock mod as it caused too many issues.
[Epic 4G Android Development] kehlan:
Well that's disappointing.

Any reference to a lockmod that works with this ROM on MTD is greatly appreciated... this wasn't what I was expecting from this, honestly -__-
[Epic 4G Android Development] jeffro18:
He might update it if people want it, i was just guessing. You can use widget locker from the market for more lock screens. I don't use it but it should work...
[Epic 4G Android Development] kehlan:
That being said, consider this a formal request for a compatible 9-lock with 3.4.2.

Thanks for the tip.
[Epic 4G Android Development] jeffro18:
I stand corrected, I see he does have a 9 lock for 3.4 listed now. I've been super busy lately and haven't checked his website in a while. I obviously haven't tried it lol. Sorry for the confusion.
[Epic 4G Android Development] drakkahn:
Well that's what I get for d/ling first thing this morning then installing later without looking at the thread again lol

Add a me to for bml Bootloop.

I would also like to add that I would be happy to test any potential fix. My phone is your Guinea pig.

Restored to backup, all is well :)
[Epic 4G Android Development] hahansen3:
I just upgraded to 3.4.2 from 3.4.1 on MTD, and no issues. Very fast upgrade!

What kernel does 3.4.2 use? I ask because I flashed Shadow-EL30-MTD_3.0+OC on 3.4.1, and after flashing 3.4.2, that is the kernel I still have.
[Epic 4G Android Development] jeffro18:
Just had some time to flash 3.4.2 lite with a few different scenarios all on mtd.

Flashed clean from cwm 5.5.0.4 after cm9 and was successful. It installed with shadow mtd EL30 v3.0+oc. Tried flashing sprint fix and 9 lock for 3.4.0 zips, with and without mounting system. Both failed with status 7 errors. Flashed green and blue mtd 3.4.2 themes successfully. The green theme boot animation is awesome by the way!

I did notice tw launcher was still present as an option in fresh flash of 3.4.2. I did not receive the ota message like previous EI22 builds recently upon a fresh flash. Looks good so far for people on mtd. I'm going to convert my 4.0 alpha backup to 3.4.2 in a bit and run with that tomorrow.

Edit: flashed 3.4.2 over 4.0 alpha and did get the ota update notification after a few minutes.

Thanks for your continued support of this project with your busy schedule.
[Epic 4G Android Development] v8bait:
If you're stuck in a bml bootloop, just install a kernel of choice and it should fix it. Cleangb and shadow both flashed over and no more boot loop.
[Epic 4G Android Development] Trident:
While I appreciate that the new server is more reliable, hopefully it's a lot cheaper. Because it's slow as molasses.
[Epic 4G Android Development] kehlan:
Are you implying that other EI22 kernels work perfectly with this ROM?

I'm about to squeal if this is true.
[Epic 4G Android Development] yaboye616:
I keep getting a dialer hang up when I enter a number and bring it to my ear, anyone else having this issue?

---------- Post added at 02:38 AM ---------- Previous post was at 02:27 AM ----------

What has been working for me is I dial the number, wait for it to connect, the bring up to ear.
[Epic 4G Android Development] RandomKing:
I have no money, I only upload to free servers. :D

Unfortunately, where one beats another in one area, it lacks in another.

I can't win.

You can use any kernel, sure.

Turns out they changed the phone.apk a fair amount more than I'd expected, so I'll probably just be putting the old one back into EI22. Of course, I'm assuming it works fine in EL30 where it came from!
[Epic 4G Android Development] RandomKing:
Testing needed

Okay I spent most of yesterday night handwriting and rewriting 10 pages of installer-scripting. Apparently it is that long. Anyway, I've finally rewritten it, simplified it, and further enhanced it.

That said, I can't currently test it on BML, only on MTD. Ordinarily I would have my testers take a look at it, but as they're generally as busy as I am, I'm right now looking for someone to test it on BML(EXT4 or RFS) as soon as possible.

Rest assured, as with 3.4.2, there is nothing in here that could brick your phone. At worst you may have to nandroid or odin restore. But I'm VERY confident in it this time. Although as usual, please back up first.

Again, first person willing to test 3.4.3 let me know. I need you to test an incremental install over 3.3 or 3.4.1, and I'd like you to test a clean install.
[Epic 4G Android Development] DaveWW00:
I am on ext4 and 3.4.1 right now. I dont mind testing it for you but wouldnt be able to do that until I got home from work tonight. Let me know.
[Epic 4G Android Development] v8bait:
I can play around with flashes this morning if you'd like. I'll be at work all day with not that much else to do.
[Epic 4G Android Development] RandomKing:
Uploading now, I'll message it to both of you. As soon as I get a definitive confirmation on EXT4 compatibility I'll release. This will change you to 3.4.3 and will revert your phone to the EI22 phone.apk. I'll miss it though, until I finish 4.0.
[Epic 4G Android Development] pixlz:
Also throwing out there for testing rom stability, installation and such. Am currently unemployed so ive way more freetime than id like. ;) i've even been nandroiding as of late so i make sure to have the clockwork folder again. If the other peeps is enough, thats plenty cool. Still rocking 3.3 BML at the moment.
[Epic 4G Android Development] RandomKing:
XDA Private messaging is failing at the moment... :mad: Link sent though.

As for the clockworkmod folder... I've fixed that! :D If you don't have one, it should create one for you.

Still waiting on a positive confirmation on the clean install and incremental install of BML.

Sorry on the unemployment, it's rough!
[Epic 4G Android Development] v8bait:
Sorry took a bit longer than I thought, got one of the famous houston speeding tickets this morning. Serves me right, was just talking about how long it's been since they've hassled me yesterday.

Anyways... here are my results on BML:

CleanGB (RFS)-->ThunderHawk 3.4.3 no data wipe:

- Installed great, pushed Shadow kernel EL30, converted to EXT4

- Lost my apps (due to RFS to EXT4) but not my contacts or settings! I kinda just forgot to wipe data but it installed perfect anyway, sorta surprised about that one

Thunderhawk 3.3--> 3.4.3 no data wipe:

-Installed fine, pushed Shadow kernel EL30, was very fast install.

I'll let you know about bluetooth later, but on 3.4.2 it still had problems turning on except after reboots.
[Epic 4G Android Development] RandomKing:
Eh, the bluetooth was a shot in the dark... I have no idea what the problem is if I didn't fix it. The Wifi/4G issue SHOULD be fixed.

As for the install, EXT4 full compatibility at last! And I have confirmed MTD many many times. Well I think it's probably safe to release. The final EI22 version. I'm hopeful that EL30 will not sport these same wireless issues, as I'm starting clean from a base deodexed EL30.

Although it issss supposed to back things up during the RFS-EXT4 conversion. Oh well. Maybe next time.

Thanks a lot!
[Epic 4G Android Development] RandomKing:
No need to be rude. Apparently I had the wrong updater-binary included causing the install to fail. It should be working now with 3.4.3.

As Jeffro mentioned, it does add instability to the phone if you're not already aware of that.

On the other hand, it currently will not be included for EL30, as updating the entire mod is beyond me.
[Epic 4G Android Development] locomariachi:
Hey Random, on my phone with 3.4.1 i'm getting crazy battery loss. I'm talking like 40% over night. It's crazy, any thoughts?
[Epic 4G Android Development] drakkahn:
Update works perfectly on BML now. BT seems to be working fine at the moment.

Thanks again for this great ROM

I'm looking forward to 4.0
[Epic 4G Android Development] JeffATL:
Yes, can confirm a successful call with bluetooth on 3.4.3 without a force close :D

Like you said, it probably had to do with mixing the EL30 dialer and the EI22 rom.
[Epic 4G Android Development] v8bait:
Whatever you did to the Bluetooth, it doesn't have initialization errors for me anymore either. Good work shooting in the dark!
[Epic 4G Android Development] pixlz:
XDA's private message fails... so anyways, installation test for 3.4.3.

okay, so the incremental installation i'm confused a bit.

it doesn't give the version number in the "MyRandomRom" in the About spot. it does though update the kernel. as a result, i'm not sure it updated properly.

As for a fresh install, coming from another rom(CleanGB V18 since it was on my phone), it does seem to work fine. No issues. Version # and everything properly displayed.

Now i did run into one hiccup. I tried the incremental install again. When i realized the version number was missing, i tried a full Factory wipe/install. The kernel was already in the system as the wipe doesn't take care of that(may be important). in any case, setup kept crashing when i would finish the boot, and as a result the launchers weren't working and it was like hitting a brick wall. I tried this again and duplicated the error.

Nothing affected ClockworkMod poorly. When the full version installed fine, i was able to make calls + send texts. i'll test the rom itself out more.

hope this helps.

also if you need any help testing 4g, i am in a 4g area as of a week ago(yay moving!).

~le poof~
[Epic 4G Android Development] JeffATL:
Unfortunately, within an hour of confirming it working I had force closes on phone app :(

I just cleared data on the phone app - will see if that corrects it since I did not clear data from going from 3.4.0 to 3.4.3...

Update: unfortunately phone app still crashes just as bad as it did on 3.4.0