yashsingh1/xdaforums huggingface dataset:
[Samsung Infuse 4G] scott.hart.bti:
No idea... dont use that at all.
[Samsung Infuse 4G] pqrs:
so excited......:victory:
[Samsung Infuse 4G] enochpc:
I swear someone posted Bluetooth was working ...
[Samsung Infuse 4G] :
NP, I'll look into it when I get home later and once you've tested and posted an update. Just wondered if the BT fixes that araemo suggested got put in - BT already worked with those suggestions, just no audio. With JT's audio fixes, I wonder if they will carry over to BT.
[Samsung Infuse 4G] The Jack of Clubs:
there are 2 chips capable of bluetooth data, but only 1 capable of bluetooth audio. it was working right in cm9 after entropy found that out. it shouldnt be too hard this time to get bluetooth working, but it may not be in this build. so just wait and find out.
[Samsung Infuse 4G] scott.hart.bti:
Wow even USB storage works... JT is a miracle worker...

Still uploading... putting up a mirror as well..
[Samsung Infuse 4G] :
I hear ya, but this part isn't necessary. Before I left for vacation, I was personally tinkering with using araemo's suggestions (that were directly related to Entropy's fixes) to try and get BT working. So, it's not an unreasonable thing for me to ask where we are on that at the moment. But yeah, waiting and finding out is no issue for me, was just wondering.
[Samsung Infuse 4G] scott.hart.bti:
Here we go Unofficial CM10 7/22/2012 - Dev host ... Mirror coming soon.

and here is the Mirror

Credit goes to JT for fixing a bunch of things... all i did was roll back a couple changes and build and throw a zip out there for you guys.
[Samsung Infuse 4G] ElPopso:
I guess you know that bt phone audio has been working fine.
[Samsung Infuse 4G] Bjray:
"Sorry, you are limited to 8 thanks per day" lol ;)
[Samsung Infuse 4G] scott.hart.bti:
Just incase anyone missed it... Will update OP shortly.

Here we go Unofficial CM10 7/22/2012 - Dev host ... Mirror coming soon.

and here is the Mirror

Credit goes to JT for fixing a bunch of things... all i did was roll back a couple changes and build and throw a zip out there for you guys.
[Samsung Infuse 4G] outta757:
Scott you did a great job and big thanks to you and the rest of the dev
[Samsung Infuse 4G] VortexJunior:
It loops in a downloading/failed on the downloads app. Any solution?
[Samsung Infuse 4G] :
In JB? No, before I left a few days ago for vacation, it wasn't. That's why I asked - I'm not even home yet to play. Calm down, boys.
[Samsung Infuse 4G] FlyingIsFun1217:
I had the same thing on the stock Gingerbread browser. Pretty much any other browser fixes the problem.

FlyingIsFun1217
[Samsung Infuse 4G] VortexJunior:
I just had to free up some SD space
[Samsung Infuse 4G] scott.hart.bti:
OP has been updated.. No longer a WIP... We are still going to resolve any issues we find and keep updating with new builds, but i believe this is definitely stable enough that it doesnt need the WIP title.

I am ALLLL smiles over here. :)

I cant say it enough.... Thank you JT. And thank everyone else that was and will continue to be involved.. Such as Yuma and araemo - You guys have done ALOT!
[Samsung Infuse 4G] :
Congrats man, and with what you've been putting into this, you certainly have my vote for RC (not that my vote counts for anything).
[Samsung Infuse 4G] papu4ara:
:victory::victory:Super Sunday Surprise :victory::victory:

Jelly everywhere :laugh:
[Samsung Infuse 4G] threi_:
Ive had the same issue a couple days ago, how i fixed it was to plug in and unplug the usb cord (it seems to happen after charging the phone)
[Samsung Infuse 4G] elliot.newnham:
I think a lot of these battery issues can simply be related that we are using a heavily modified Gingerbread kernel... There is very little here given to us by samsung. It is incredible that it even works at all. Scott has done such a great job with it so far, just give him time! :)
[Samsung Infuse 4G] DaMeatMan:
I had the same problem after a while. I found the problem to be related to Media Storage. To fix the problem I went to SYSTEM SETTINGS --> APPS --> go to all apps so system apps are displayed, select MEDIA STORAGE then CLEAR DATA. After a reboot I found that my device was now able to enter deep sleep finally.

Just as an FYI, this seems like a common issue with Jelly Bean in general and not necessarily anything related to Scott's ROM in particular. After allot of searching I found this to be common even across stock ROMs on certain phones. I believe someone mentioned a while back that media scanner may have issues with reading the SD card. Formatting may also help fix the issue, but in my case a format was not necessary and clearing data fixed it for me.

Slap thanks if this helped any of you ;)
[Samsung Infuse 4G] scott.hart.bti:
How about all the people *****ing that they are having so many reboots and this and that provide a god damn logcat or any information that could be useful for a change

And there is NOT a battery issue, but sure... ill look into it.

This is exactly why i was hesitant about adding OC...
[Samsung Infuse 4G] erezsegev:
Upgrade from 2.3.6

Hi,

I have rooted my stock rom 2.3.6 via Odin.

I would like to go with CM10.

In the instructions it said:

"Make certain you are on ICS, this can be done by flashing Entropy's CM9"

1) Do I need to flash to CM9 or I can go directly with CM10?

2) Do I need to place the CM.zip on my phone, If I need to remove the SD?

Thanks for the help.
[Samsung Infuse 4G] thushianthan:
After rooting you have to install CWM. Via CWM you have to install CM9 then CM10.

GOOD LUCK !
[Samsung Infuse 4G] erezsegev:
Upgrade

Thanks,

I will install CM9 before CM10.

Where do I put the CM10 if I remove the SD card?

Does it take it automatically from the phone?
[Samsung Infuse 4G] ibCurlyFry:
Slap it in the internal SD card

i believe its:

/mnt/sdcard

for CM9 :silly:

The external SD is the one you be removin
[Samsung Infuse 4G] Clark Joseph Kent:
All,

Thread Cleaned & if you feel to need to express your feelings you can PM the OP, but this is about Development....there seems to be some questions here, but what is listed in the OP is simple:

If you have an issue and you want to call our attention, here's what you do:

1. Try everything you can, find solutions for yourself. Wipe caches, revert all your settings you have made, go back to your stock Kernel, factory reset if you have to or reflash the rom. Assume that the issue is on your side and try your best to isolate it.

2. Search this thread and Cyanogenmods aswell (its our base) for possible reoccurences of your issue and hopefully solutions that may have come up.

3. If you think the issue is important enough that we should cease our work and look into it, post your issue, BUT ...

... stay friendly, do not demand anything, do not threaten

... explain your issue as precise as you can, name the exact apps and conditions that cause trouble, help us to replicate the issue right away. If we can't there's no way we can fix it and your post will simply clutter the thread

... collect evidence, keep in mind this is a developer thread so even if you are not one, do us the favor and research how to record logcat. logcat is the single most important help you can give us to resolve your issue.

Thank You
[Samsung Infuse 4G] veener79:
I had this happen too on Friday. I did not have a log running at the time since the rom was running great. When I looked at my battery stats it showed my "phone" had been running for over 30% of the time of the about 2 hours my battery lasted. I had only made about a 2min phone call. Looks like the app got hung up or something.

I have had a few random reboots now and then. I would say less then a dozen in the 2 weeks we have had this ROM version. Far as I know it could be a app causing the issue.
[Samsung Infuse 4G] PoXFreak:
How about putting ALL the files you need into a folder called "Roms" on the internal SD card? That way you don't have to connect/disconnect from a PC so many times... Then delete the files you don't need to regain the space.

Make SURE you wipe /data and both caches before and after flashing each firmware!

First off, what network and where are you located regionally?

Att has been doing a LOT of upgrades here in the southeast, and the towers will drop out their 3g coverage in groups (it seems), to help keep network triangulation up and running.

One thing to check is go to phone and type *#*#4636#*#*. Then phone information. There is a drop down box that allows you to change how the ROM handles the cell networks, this should say "WCDMA Preferred" if on att or straight talk. If it doesn't, change it to make it say as above. I would assume Rogers is the same since it uses the same network type.

You should at least airplane on/off once after doing this to reset network status.

Hope it helps...
[Samsung Infuse 4G] PharmNerd:
Not a logcat, but here's a god damn last_kmsg. :)

Phone was sitting on the end table and rebooted itself, getting stuck on the CM boot animation. Did a long-press on the power button, and then pulled this last_kmsg after it rebooted. Not under/overclocking. Using the 10/27 build still.
[Samsung Infuse 4G] scott.hart.bti:
All: I will get an update out tonight... The only thing i can think of that is causing these issues for some people is the very minor kernel changes i made... Obviously our kernel is unstable and any change no matter how minor causes pandemonium for some. Ill revert my changes and push out an updated kernel to flash which should take care of the issue.

Are people having the issue with the latest build or the 10/27 build as well? If its the 10/27 build as well, ill have to revert the OC changes. And for 10/27, i dont want to hear about 1 reboot in 3 weeks.. i only want feedback if your having ongoing issues.
[Samsung Infuse 4G] deathblade:
For everyone who is having constant reboot try this, enable zram by going into settings/performance/memory mamanagment/zram click on 35% then make sure doth check marks beneath are checked then reboot recovery wipe cache and devalic cache and reboot see if that helps
[Samsung Infuse 4G] scott.hart.bti:
Come on... lets get some feedback here... people want to post 900000 times about the same thing, but dont want to say anything when im willing to take a look.
[Samsung Infuse 4G] psal217050:
Only rebooted on 11/4 ROM. No over clocking either, max is 1200. Sent PM with links to logcats.
[Samsung Infuse 4G] kalebdevil:
My phone have no issues no random reboot only the best battery life that I never gets with other ROM, sir what a great job with 11/04. Hope this new release may contain 4.2 updates, keep doing this superb job....
[Samsung Infuse 4G] scott.hart.bti:
For those of you having issues with reboots, download and flash THIS Kernel. I reverted some of the minor changes. I have no idea why some of you were having horrible problems and why some of you were not, but i guess that pretty much indicates how horrible F'ed our kernel is and that the smallest freaking change causes havoc for some users. Going forward, im not even touching the kernel or looking into changing anything kernel wise unless its a standard cm change for ALL samsung kernels.

Anyways... download from above, reboot into recovery, wipe cache, wipe dalvik cache, flash kernel fix, reboot.
[Samsung Infuse 4G] hattrickinc:
My phone rebooted for a couple hours last night. I'm researching how to get the logcat so I can post it here.

..talk about timing lol
[Samsung Infuse 4G] scott.hart.bti:
Do not bother providing logcats or reporting it... just flash the fix... no sense in beating a dead horse... since i provided a fix and put the download link on the main page, i do not want this thread to continue to be flooded with the same thing over and over. Flash the kernel and if issue continues, then post about it.
[Samsung Infuse 4G] hattrickinc:
Attached.. I believe it happened about 0700-1300 today.

This reboot problem has happened for at least a couple ROM updates.

*runs for cover*
[Samsung Infuse 4G] PharmNerd:
Screw it. Never mind.
[Samsung Infuse 4G] scott.hart.bti:
Seriously... I have already fixed the issue that you guys are experiencing and posted a fix.. Why is this still being discussed?

And starting to get irritated.
[Samsung Infuse 4G] pinktheater:
when I did my phone I didn't remove the sd card and everything went smoothly.

I actually had issues the time I removed it.
[Samsung Infuse 4G] PoXFreak:
I've had a lot of silly stupid things happen across almost all the builds...up until recently. Being one of Scott's lead testers on past builds, I have had nothing but good luck and decent battery life from the last few builds.

Give it time, make sure you followed instructions, and make every attempt to correct things yourself before you go haunting a dev to fix something that isn't broken.
[Samsung Infuse 4G] BravoMotorola:
I completely agree. Guys stop being bltches.
[Samsung Infuse 4G] slipnslider:
I just want to chime in and say the 11/4 build has been the most stable build and the best build for me yet. Battery life is great. I get no random reboots and no other problems. I can't wait for 4.2!
[Samsung Infuse 4G] wickedninjalo:
Thank you for your fix Scott. Just remember... you da man
[Samsung Infuse 4G] FlyingIsFun1217:
I'm sure you hate having to revert changes, but the patch you put out worked wonders on the battery drain issue I was having. I now am no longer stuck never going into deep sleep.

FlyingIsFun1217
[Samsung Infuse 4G] MrBooMY:
Thanks so much Scott! I'm learning how to get logcats so I can be of more help if any more weird issues crop up. So far so good!
[Samsung Infuse 4G] j.smith:
Perhaps this is a dumb question, but why is the Infuse on the kernel version it's on right now (a GB kernel or whatever)? I have wondered this since Scott says this is all we can use, but some searching and I couldn't find why a phone would be locked to a specific kernel.

Is it because of what Samsung has(n't) released to the community? Just curious, since I have a Captivate as well which for whatever reason (unknown to me!) it's supported by CM and runs a 3.4.x or something kernel even though I would have thought that since that phone was older than the Infuse, it would be even less supported or something.
[Samsung Infuse 4G] zacharysblubaugh:
Hey Pox how is it coming trying to get 4.2 without cm any luck yet

Sent from my Samsung Infuse running PA JellyBean using the xda-developers app
[Samsung Infuse 4G] blrumph:
Please help

Ive been running your 11/04 version of paranoidandroid ever since it was released. I havent had any problems with it until last night. Its stuck in a boot loop in between the samsung and galaxy s logos. The worst part is, is that I cant get this into recovery mode or download mode. When trying to get it into download mode (for unbricking) right at the moment when I insert the battery, it automatically goes back into the bootloop (without pressing the power button) instead of showing the options for going into download. Right now, im phoneless typing this message from a computer. Please, if your have any advice tell me. I;m desperate to get my phone back working. i just need help
[Samsung Infuse 4G] openwheelracing:
Since I haven't had an issue I won't flash this kernel. I will wait for that sweet Jelly Bean 4.2
[Samsung Infuse 4G] hattrickinc:
Reboot happened again, after flashing earlier today. Will post logcat tomorrow
[Samsung Infuse 4G] Dani897:
the captivate is purely an Aries device. once the mtd conversion is done it likely runs from all nexus s drivers on the nexus s kernel or maybe a newer Linux kernel. the infuse is a hybrid of Aries an another platform (crespo was it? ). the infuse drivers don't compile if you change the kernel version even though they are very likely compatible in most regards. there may be a way to update things and clean them up but I don't know that much about it, my brother is the real Linux guru. its probably possible to get a newer kernel using drivers and libs from other devices that share hardware and editing some source code for the infuse. but its a lot of work and will likely have more bugs. not less. the lack of cm official support has less to do with Samsung and more to do with the long standing bugs we had like Bluetooth support. had Linux bozo figured out the Bluetooth chip before ics came out then worked on mtd there is a good chance we would have had cm support but without the hardware fully supported in cm7 and lb moving on to gnex things stalled for a while. then some things that worked great on cm7 don't on cm9+ like the camera, now we have something very close to being able to get cm support but by the time it happens android 5.0 may be out and we may only get minor maintenance on cm10.1 there after if the hardware criteria changes. the lack of a newer kernel may be that they haven't fixed the camera bug on the old one yet. and the work it would need to put together all the pieces for a 3.x kernel. it may eventually happen if everyone doesn't move on to new devices.

don't get too wrapped up in kernel version numbers either. after 2.6.39 (I think) Linus torvolds (spelling? he's the inventor of the Linux kernel hence the name) decided to change the naming scheme. the old scheme was major version>minor version> revision. Linus decided to change it to major version>revision only and started the numbering over at 3.0. all the 3.x kernels are arguably still in the 2.6.x series. but it has gone through something like 8 more revisions.

my computer is running on a 3.2 kernel now. but I'm thinking about starting over with a LFS (Linux from scratch) install so I can get familiar with the building process and update to the newest kernel revision. I have compiled cm from source just to do it but its pretty automated. it didn't exactly give me much more of the picture than I already had. I'd try to teach myself more but the infuse is the only working phone I have, its hard to get experimental and then have to unbrick then flash ics then a working mtd jb build to go back to work the next day. maybe when i get my next phone I can use the infuse as a hack/teaching toy. but even on basic things with Samsung ROMs I had trouble getting things done because i'd make mistakes and have to unbrick and lose interest....

guys that dev on their primary phone deserve a ton of credit.
[Samsung Infuse 4G] omar71693:
Same here!
[Samsung Infuse 4G] PoXFreak:
Haven't had much luck as of yet... Most of the things I'm running into are "cosmetic", libs from one being ported to the other and not working (audio for one). I do get it to boot, but even after changing build.prop and default.prop values, its as if it wants to remain 4.1.2 for some odd reason.

Without a true build environment I'm not going to get very far, especially working without openjdk or sun java dependencies.

I'm gonna start fresh tonight with a clean hard drive and Lucid Lynx, then find out why I can't get a java package to install correctly.
[Samsung Infuse 4G] zacharysblubaugh:
Sounds like most of it that can go wrong has gone wrong

Thanks for all you've done so far I hope you get java running (with lucid would you need a special package or will .deb work, kinda curious I tried some but not very hard to install a few programs in it)

Sent from my Samsung Infuse running PA JellyBean using the xda-developers app
[Samsung Infuse 4G] pinktheater:
I was on 10/26 until last night that I decided to move to 11/4. I had a reboot but I installed the fix provided by Scott.

Not only the reboot never happened again, but my battery life improved and the signal went back to what it was before, awesome!
[Samsung Infuse 4G] thushianthan:
Yep !. Battery life is improved with compared to 11/04
[Samsung Infuse 4G] araemo:
Basically, it would take a LOT of effort to make a 3.0.x kernel work on the infuse, and making it 'work' is still not the same as making it work 'as well as' the current 2.6.x kernel. And really, most android devices are running ancient kernels.. as for captivate, it runs 3.0.x, not 3.4.x. Even my SGS3 only runs 3.0.x. I've considered doing the work, but have lacked the motivation, since it's opening a can of worms to make that kind of kernel change. (Honestly, my preferred method would be to take the aries kernel (captivate, fascinate, etc), and start adding the infuse-specific drivers to it. I actually started on that a month or so ago, but got distracted.)
[Samsung Infuse 4G] hazard66:
isn't that what "[ROM][JZO54K-4.1.2]~Jellybean~AoCP CP 4.6~The Collective (11/19/2012)" is based on?

just curious!
[Samsung Infuse 4G] PoXFreak:
Yes and no; I have installed Aries specific firmwares to the infuse without much trouble. The captivate is just the specific build type that comes up in about phone under settings. The kernel is the main deciding factor in whether a firmware will or won't function on a specific device. Back when the kernel had to be reworked to allow ICS to run, there was a LOT more wrong with the kernel (and drivers), specifically audio, Bluetooth and WiFi all suffered some, but if I remember correctly there was more issues with the kernel than with firmwares.

All this mess started with Honeycomb and continued through ICS, since ICS was the bridge between tablet and phone. Before honeycomb there really wasn't a tablet-specific android firmware. Honeycomb was that firmware, and ICS was an either-or firmware that could be built for phone or tablet.

Take a whole bunch of Aries, add some crespo to it, squeeze in a whole lot of Maguro and this is what you get; the phone we all love and enjoy owning.

Sorry, long post... Boring day at work. :D
[Samsung Infuse 4G] threi_:
*nvm*
[Samsung Infuse 4G] araemo:
How should I know, since they don't post a link to their source? (Downloading it anyways to investigate the kernel, but still.. not posting your source on a 'source-based' rom is bad form (and possibly a violation of copyright).)
[Samsung Infuse 4G] hazard66:
yeah :(

i had asked them if it was based on scott's kernel tho and they said:

"It is based on teamhacksungs kernel via Dman, and yes it is MTD based. As far as I know, I'm not sure if you will have to Odin back to stock, I guess we will find out soon enough... "
[Samsung Infuse 4G] araemo:
Yes, but there are multiple versions of the aries kernel in teamhacksung's repo. So, that tells me very little. and 'based on' doesn't mean 'we didn't change anything to make it work'. Also, I don't see where it says it's based on an aries kernel at all. Teamhacksung does have a dempsey kernel, which is what jt did his infuse work on.
[Samsung Infuse 4G] BravoMotorola:
So I put this on my friends infuse. I played with it for 30 minutes hardly believing how well it ran. Battery life is good too. Thanks for all of the work, the phone is just incredible now.
[Samsung Infuse 4G] spdivr:
I'm bummed. I installed the 11-4 rom, the updated kernel, the kernel fix and the gapps, but the phone seems to have issues. Time zone was off and it seemed to have worse radio reception. I tried reinstalling a couple times, did the whole wipe routine, but no luck. I had to go back to the previous rom. Anyone know what might help on mine?
[Samsung Infuse 4G] deathblade:
Time zone is your carrier which you can change manually as for signal try a different modem I would suggest kl2 and I would suggest doing so before reporting a false issue, I don't mean to sound harsh, but its getting rediculious with people not doing any investigative work and just saying oh something is wrong with the ROM
[Samsung Infuse 4G] spdivr:
I didn't say something was wrong with the rom. I know that is not the case due to the number of people who have had great success. I've had good results with the other roms, this was a change from past experiences, so I figured it was something to do with my phone or process.
[Samsung Infuse 4G] aznracer62:
This was already discussed here and in the Q&A thread a few pages back. Please search first before you post. If your time zone is displaying incorrectly, read up on the past few pages and you'll get your answer. Let's not start this time zone discussion all over again.
[Samsung Infuse 4G] zacharysblubaugh:
Cm is getting close

Its almost time for some NEW JellyBean

Sent from my Samsung Infuse running PA JellyBean using the xda-developers app