the end of august is fast approaching and no update for a few weeks now.. there are rumors of gps fix in the works. and better gps in the african latest august release.. how about a release newer than jm5 thanks.
I read somewhere that the Russian guy who was leaking the FW's got caught and although he didnt get sacked he has been told no more leaks.
alferret said:
I read somewhere that the Russian guy who was leaking the FW's got caught and although he didnt get sacked he has been told no more leaks.
Click to expand...
Click to collapse
hes lucky sammy good job for not sacking him
It's a shame . I don't understand. The samsung just had to win with this situation. Everyone knows that the best beta testers are the people of XDA.
Now what do I do with my life without one (or five) firmware a month to test: '(
Hope it's not true
Actually there is a newer version: The official JM1 which is not to be confused with the inofficial JM1
This Version is said to sport some updates over the most current inofficial 2.1 JM5 build.
There is a trick getting it which involves flashing the phone back to JF3 and then getting an update via Kies by accessing a test mode (done by: Ctrl+Alt+u+p)
There is a german thread visable here: http://www.android-hilfe.de/root-ha...ielle-update-jm1-jetzt-schon-zu-bekommen.html
I for one am sticking to JP3. It's not the smoothest but definatly the most good looking and I am hoping for a new 2.2 build in the near future. The browser is just sooo much better than eclair!
i am sure sammy didnt want any very "young" firmwares to leak to the public. i am sure that we will get a leak by the end of the month, but a pretty much almost ready for launch one. they prolly want to take care of good implementaion of froyo features ( JIT mailnly) before anything goes out, even if leaked.
I am having withdrawal effects from not flashing any firmwares... IT'S BEEN ALMOST 2 WEEKS SINCE MY LAST FLASH! lol I'd never gone so long without a flash since I got the phone. I do have to say that JM5 with the ext2 lag fix works very well and I don't plan on flashing unless I see people getting significant improvements, or a stable froyo firmware. I think Sammy should leak and let us point out the bugs haha, even if it's early builds...
yeah what's with the lack of leaks firmwares seriously with my touch HD I was flashing every other day Not having new firmware to flash is really "unusual" for me. I want firmwares
Someone claims to have upgraded to JM6 through kies. This would be great as it would be the newest official firmware I think.
http://forum.xda-developers.com/showpost.php?p=7743693&postcount=121
Related
I tried the Cyanaogen Froyo build and it keeps locking up, so I have to keep pulling my battery to restart I think the killer was when I followed someones guide for tweaking the ADW launcher.
Currently there aren't any ROMs out there that are stable and full working. I do know that Cyanogen is going to finish his ROM soon, which will be exciting. But, I like HTC sense so DamageControl is going to come out the a Froyo ROM including sense as well. They will be releasing their ROM soon (In the bout 2 weeks, maybe less). There has been a delay since the main developer for DC broke his phone when he let his wife have it (never trust women with phones ) I am looking foward to flash both of them!
PAPutzback said:
I tried the Cyanaogen Froyo build and it keeps locking up, so I have to keep pulling my battery to restart I think the killer was when I followed someones guide for tweaking the ADW launcher.
Click to expand...
Click to collapse
Uhm...the Cyanaogen build is still going through nightly build phases. This is not even a ready for prime time build and you seem freaked out that it doesn't work. I totally support all the guys running this thing the evening it was released...but that's not me.
I will wait a few weeks till they have an official release thread.
Love the idea of this, but I am not an early adopter and that is what Froyo is...early adopter status/level. They only just recently started pushing 'official' versions to phones...so to expect the volunteer devs to have one ready is kind of unreasonable.
If you want earlier adopter stuff....have fun...but it could do what you experienced. Just don't expect final stuff so quick...heck the phones have been out what...~5weeks now???
sablesurfer said:
Uhm...the Cyanaogen build is still going through nightly build phases. This is not even a ready for prime time build and you seem freaked out that it doesn't work. I totally support all the guys running this thing the evening it was released...but that's not me.
I will wait a few weeks till they have an official release thread.
Love the idea of this, but I am not an early adopter and that is what Froyo is...early adopter status/level. They only just recently started pushing 'official' versions to phones...so to expect the volunteer devs to have one ready is kind of unreasonable.
If you want earlier adopter stuff....have fun...but it could do what you experienced. Just don't expect final stuff so quick...heck the phones have been out what...~5weeks now???
Click to expand...
Click to collapse
I'm not freaked out. And I doubt it his ROM rebooting my phone as much as it is something with SetCPU not being updated for 2.2 or some other app. I am back on Damage and I do like the HTC Sense apps that just work. I am looking forward to Damage's version of Froyo.
I dont know if this JPD is the Same as JPC, this the link:
http://www.multiupload.com/UNYY3TTQPQ
Hope this is better than JPC.
I'm not flashing again untill i know its a stable release...
JPC sucked bigtime... memory issues which made me reboot the phone every day, or it made launcher pro reboot everytime...
Changelog please, or prior differences to JPC..
Sent from my GT-I9000 using XDA App
BackfireNL said:
I'm not flashing again untill i know its a stable release...
JPC sucked bigtime... memory issues which made me reboot the phone every day, or it made launcher pro reboot everytime...
Click to expand...
Click to collapse
weird..JPC hasn't given me any problem... did you wipe ??
looking for reviews about JPD
just flashed to JPC 4 hours ago.. now come out another 2.2!!!
Jep i did! i had issues with browsing... when i visited several flash pages the whole memory filled up... and i couldn't free up ram with any task manager...
I think JPD is stable because they used it on I9000's on the IFA
Had troubles with JPC too... will give it a try...
So.. No one tried this yet?
Again another bs "release" by Samfirmware.com.
They seem to have no clue what they are doing.
This is the very same I9000XXJPC release, which was already released last month.
Also I recon this version is not bootable after Odin flash since it is a "high" release.
Someone go try it lol
Richthofen said:
Again another bs "release" by Samfirmware.com.
They seem to have no clue what they are doing.
This is the very same I9000XXJPC release, which was already released last month.
Also I recon this version is not bootable after Odin flash since it is a "high" release.
Click to expand...
Click to collapse
Your the one i'm following for new firmware releases ... do you have any idea when samsung will release JPD? i know they used it on I9000's on the IFA show.. could you shed some light on this?
Update: https://twitter.com/SamFirmware/status/23073587427
The cake was a lie!
Downloading it now... 151 MB seems a little bit odd but i just wait..
And...hmm.... yeah... my internet is verrrrrryyyy slow so i need quite some time but if no one else will try it i am gonna post my results ^^
Edit: Screw it... too slow again -.- Just read the post above mine
After JPC fail.... guinea pigs no more
kalpik said:
Update: https://twitter.com/SamFirmware/status/23073587427
The cake was a lie!
Click to expand...
Click to collapse
lol
love the cake song
Hmmm.... i loled xD
Just trying it now.
Doesnt seem to get very far using the 803 pit, trying 512
BackfireNL said:
Jep i did! i had issues with browsing... when i visited several flash pages the whole memory filled up... and i couldn't free up ram with any task manager...
I think JPD is stable because they used it on I9000's on the IFA
Click to expand...
Click to collapse
So does that mean that the JPD is in fact the real deal??
Cheers....
Edit: disregard my last. I kinda jumped the gun thinking that this, in fact, was another Froyo release. Moved on to page 2 of the thread, and BAM.
skiddhard said:
So does that mean that the JPD is in fact the real deal??
Cheers....
Edit: disregard my last. I kinda jumped the gun thinking that this, in fact, was another Froyo release. Moved on to page 2 of the thread, and BAM.
Click to expand...
Click to collapse
Downloaded it, but did not flash...! thought just waste of time...
Seems a joke to me... All the files have the same build date as JPC 26th of aug... hehehe...
Ok, I am currently on contract with sprint until the end of next august. I was disappointed with the extended delay/final build of Froyo for this thing, and still trying to play the usuall waiting game on Gingerbread right now. My Epic i currently still "pure" and not rooted. I really don't want to risk Rooting it, but at this point I feel I should. I've been researching this for a while now but all I could come up with were very old articles,build roms, belated possible dates & info on the epic touch. Only thing I could get out of contacting sprint some time ago was the usuall "it's coming soon" I'm not the patient type.
So...you think I should quit my risk full induced hesitancy and root my phone then and there, or simply be stuck with froyo and keep playing the waiting game (If they don't decide to abandon releasing the build in favor of sticking with the new 4.0 /GSII lines).
I've got to say that for me the upgrade from Eclair to Froyo made a huge improvement in my Epic. I've rooted the phone so I can run various backup and and adblocker apps, but every time I try custom Froyo ROMS I end up going back to stock because of some odd problem or crash or something that doesn't work.
Right now I'm trying the Gingerbread EH17 leak with the source code compiled kernel, which is the most stable Gingerbread I've found. Is it better than Froyo? Yeah. Is it a lot better? nope. On a scale of 1 to 10,the upgrade from Eclair to Froyo went from 5 to 8, the upgrade to Gingebread takes it to 9. Graphics are a bit smoother, there are a few more options on some apps, Video calling is supported. Nothing to get too antsy about.
By the way, rooting Froyo is easy using the one-click method. Rooting Gingerbread requires using Odin right now, which makes it possible to brick the phone by checking the wrong options, although just reading the instructions carefully should make it pretty safe.
Jbluna said:
Ok, I am currently on contract with sprint until the end of next august. I was disappointed with the extended delay/final build of Froyo for this thing, and still trying to play the usuall waiting game on Gingerbread right now. My Epic i currently still "pure" and not rooted. I really don't want to risk Rooting it, but at this point I feel I should. I've been researching this for a while now but all I could come up with were very old articles,build roms, belated possible dates & info on the epic touch. Only thing I could get out of contacting sprint some time ago was the usuall "it's coming soon" I'm not the patient type.
So...you think I should quit my risk full induced hesitancy and root my phone then and there, or simply be stuck with froyo and keep playing the waiting game (If they don't decide to abandon releasing the build in favor of sticking with the new 4.0 /GSII lines).
Click to expand...
Click to collapse
If you waited this long, you might as well wait for the Gingerbread OTA...who knows maybe you'll be the first to get it! Wasn't Castro08 the first to get EC05 OTA? You'll be instantly famous
Sent from my Nexus S 4G using xda premium
Jbluna said:
Ok, I am currently on contract with sprint until the end of next august. I was disappointed with the extended delay/final build of Froyo for this thing, and still trying to play the usuall waiting game on Gingerbread right now. My Epic i currently still "pure" and not rooted. I really don't want to risk Rooting it, but at this point I feel I should. I've been researching this for a while now but all I could come up with were very old articles,build roms, belated possible dates & info on the epic touch. Only thing I could get out of contacting sprint some time ago was the usuall "it's coming soon" I'm not the patient type.
So...you think I should quit my risk full induced hesitancy and root my phone then and there, or simply be stuck with froyo and keep playing the waiting game (If they don't decide to abandon releasing the build in favor of sticking with the new 4.0 /GSII lines).
Click to expand...
Click to collapse
There is really no disadvantage to rooting your phone. There is a program called odin which you can return your phone back to 2.2 android. To root your phone all you have to do is copy a few files to your sd card and run a .bat or .sh (windows or linux) .
Rooting your phone puts you in control. You can remove programs that bug you or keep starting on there own. You could also put on a different rom. If you need more help let us know.
Wait it out. You're really not missing out on much. just a different version name and color scheme to be honest. So unless you got some girl at home waiting for you to wow her with a phone that's running GB. Take a number, sit back and worry about bigger things in life.
Sent from my CM7.1/*Apocalypse-Talon* v3.2.1 NS4G
.OmEgA said:
Wait it out. You're really not missing out on much. just a different version name and color scheme to be honest. So unless you got some girl at home waiting for you to wow her with a phone that's running GB. Take a number, sit back and worry about bigger things in life.
Sent from my CM7.1/*Apocalypse-Talon* v3.2.1 NS4G
Click to expand...
Click to collapse
+1, gingerbread is a little better than froyo, but nothing overly awesome about it. Cm7 (gingerbread) is pretty *****in, but u can do that from ec05...
Sent from my SPH-D700 using XDA App
Jbluna said:
Ok, I am currently on contract with sprint until the end of next august. I was disappointed with the extended delay/final build of Froyo for this thing, and still trying to play the usuall waiting game on Gingerbread right now. My Epic i currently still "pure" and not rooted. I really don't want to risk Rooting it, but at this point I feel I should. I've been researching this for a while now but all I could come up with were very old articles,build roms, belated possible dates & info on the epic touch. Only thing I could get out of contacting sprint some time ago was the usuall "it's coming soon" I'm not the patient type.
So...you think I should quit my risk full induced hesitancy and root my phone then and there, or simply be stuck with froyo and keep playing the waiting game (If they don't decide to abandon releasing the build in favor of sticking with the new 4.0 /GSII lines).
Click to expand...
Click to collapse
Ok first of all don't be afraid of rooting
2nd if you want out of your contract DO NOT TAKE NO for an answer from them! after the crap ass GPS on DI18 & more crap with EB13 & the camera not working right, I got out of my contract with sprint.
You just have to get past the "gate keeper" thats the first & some times the second person you get on the phone. All you have to do is start talking **** (with out cussing ) to them about the "crappy updates" & if they try & blame samsuck then you go into the fact that there NAME "SPRINT" is plastered on the fount of the dam phone & if there name is on something then they need to own up & take responsibility
[Q] "Your device is up to date" error. Anyone know what the heck is going on?
So here it is, four days after the ICS update was "released" and I still have not gotten an update. My A100 used to give the "network coverage is currently poor" message when checking for updates. Acer acknowledged this error, and now my device says "your device is up to date". It obviously is not. Has ANYONE heard anything from the ghost town that is Acer's support? I just feel like I'm being left out and Acer couldn't care less. They need to make a statement about this.. Or maybe they have and I missed it somehow. Anyway, could someone please offer some Insight?
Or at least, it would be (oddly) comforting to know that other people are experiencing this.
Misery loves company. My A100 is also "up to date" still on Honeycomb. At least there is hope, my phone will never get ICS (Galaxy S 4G)
have you guys flashed a rom to it? or is it stock?
Im just stock, trying to do it by the books, although acers proverbial book appears to be written in latin.
WackyClash said:
So here it is, four days after the ICS update was "released" and I still have not gotten an update. My A100 used to give the "network coverage is currently poor" message when checking for updates. Acer acknowledged this error, and now my device says "your device is up to date". It obviously is not. Has ANYONE heard anything from the ghost town that is Acer's support? I just feel like I'm being left out and Acer couldn't care less. They need to make a statement about this.. Or maybe they have and I missed it somehow. Anyway, could someone please offer some Insight?
Or at least, it would be (oddly) comforting to know that other people are experiencing this.
Click to expand...
Click to collapse
Just flash the official from. Dev section.
Sent from my A500 using XDA
ICS update
I flashed to the leaked version of ICS about a month ago. I also get the "Device is up to date" message when I try to update. Is there something I need to do since I have the leaked, unofficial release on my tab?
I am in the "I am running Stock, never even rooted the thing, and still no ICS update" boat.
Though in fairness the Acer support page says the rollout is in stages and that it would take a full week for the rollout to be complete. I am not going to officially panic until next Monday (May 7th).
truthfully it is very easy to just flash the new stock ROM. I would just go that route and if you flashed a prereleased ROM. I don't believe you will get an update. Just make sure that you put it in the correct place is the biggest mistake.
Am I the only one who's just running 3.2 ? I did a factory reset and it went back to 3.2, where as before I had 3.2.1
weird
GEN2 & PA_CA owners
Folks,
You are not alone. Many A100s aren't receiving ICS.. Mostly GEN2 with 3.2 build doesn't get any updates from Acer...same for some PA_CA builds..
Acer asked some of the GEN2s to be shipped for a manual update.. but they are not openly admitting the issue with GEN2 builds..
You have two options.
1. If you prefer to get the ICS from Acer, Flash your device to GEN1-3.2.1 and you will get the ICS update. I used this method and my A100 is on ICS now. Refer the Page 3, Post 25+ on the below thread.
http://forum.xda-developers.com/showthread.php?t=1623543&page=3
2. You can also directly Flash to Leaked final ICS from acer... below thread has all of them. go for 012 ICS.
http://forum.xda-developers.com/showthread.php?t=1591235
NewWizz said:
Folks,
You are not alone. Many A100s aren't receiving ICS.. Mostly GEN2 with 3.2 build doesn't get any updates from Acer...same for some PA_CA builds..
Acer asked some of the GEN2s to be shipped for a manual update.. but they are not openly admitting the issue with GEN2 builds..
You have two options.
1. If you prefer to get the ICS from Acer, Flash your device to GEN1-3.2.1 and you will get the ICS update. I used this method and my A100 is on ICS now. Refer the Page 3, Post 25+ on the below thread.
http://forum.xda-developers.com/showthread.php?t=1623543&page=3
2. You can also directly Flash to Leaked final ICS from acer... below thread has all of them. go for 012 ICS.
http://forum.xda-developers.com/showthread.php?t=1591235
Click to expand...
Click to collapse
Yep no doubt. I was flat out told by Acer they have had issues with pushing OTA updates to some Gen2, and asked me to ship my A100 in to have it updated...right... So I used the leaks, and now Im on FlexReaper no regrets.
I like my tablet nice hardware for the price IMO, but the firmware support from Acer sucks big sweaty donkey balls.
Make sure that your Version is 3.2.1 and not 3.2.1+ like I had. I flashed the update I got from acertablet forums, which I think they found it here, and I then had 3.2.1 and then 2 updates later I am running 4.0.3.
I shouldn't have to do any of that S***. I'm probably just going to sell this thing, because acer is filled with a-holes. GTFO Acer.
This really is embarassing on Acer's part. I was excited to get ICS but the A100 is not my primary tablet and I don't really feel like bothering with flashing it myself. We've gotten OTA updates before with no problem, why can't they make this one work?
Thanks XDA!
I too have been trying to do the official update on my generation 2 stock unrooted or modified A100. A couple of days ago I got the 3.2.1 update but nothing else. I kept going to settings checking for the update and it always came back with the software up to date message. Today I got so fed up with it that I reverted back to pre-update 3.2 by following a thread in this forum and re-ran the update check...Bingo! it updated twice. Now I have a smooth running ICS A100. Don't wait for Acer! Something is wrong with the way this Tablet checks for the update!
Just got the update!!!!!! ..for 3.2.1...............
hope ICS is to follow.
ICS
I just got the update of OTA ICS after 3 updates, and I was on Android 3.2.1 gen2.
It seems Samsung has realized their stupidity in releasing a software update for the Captivate Glide where the keyboard lights don't work and they pulled the plug on the I927UCLH2 update. They have released a new update, I927UCKL1 based on, wait for it... Gingerbread 2.3.6!!!
I would assume this is virtually identical to the previous 2.3.6 build, and is released as an update for the people who have a fairly unusable 4.0.4 device at the moment. The average user isn't able to roll back to GB to have a fully working phone, so they release an "update" for people to use until they fix the serious issues in ICS.
I think it's for people who had not upgraded to ICS are were still in the original GB 2.3.5 firmware. If you upgraded to the ICS build, connecting your phone to Kies will tell you that your phone does not support firmware updates through Kies.
cinguliano said:
It seems Samsung has realized their stupidity in releasing a software update for the Captivate Glide where the keyboard lights don't work and they pulled the plug on the I927UCLH2 update. They have released a new update, I927UCKL1 based on, wait for it... Gingerbread 2.3.6!!!
Click to expand...
Click to collapse
Neither of the ICS ROMs available are official releases. The situation is quite the opposite to what you posit -- they KNOW there's problems with their ICS ROMs and have justifiably delayed the release. What we have are leaks from their development process, and they're giving us a rare glimpse into the current state of development and why it's taking so long.
-E- Furthermore, we had UCKL1 *LONG* before UCLG9 was leaked. You're getting your order of events seriously screwed up.
Actually Samsung released an OFFICIAL update but pulled it. Research before you post.
sent from my captivate glide running ICS (NardROM 0.4 Rooted)
I would not be surprised if Samsung played it this way on purpose. Most smartphone owners aren't as eager for updates as we are, as long as the phone works.
I'm absolutely sure Samsung monitors this board and other places online, so it may very well be they released the previous update so we would test it for them. Why? Because we're happy to get the update, even with bugs. We're happier than having to wait longer, in any case. Secondly, we'll point out the most annoying bugs for them the fastest, because we're the actual users. And, of course, we're for free...!
It's one of the aspects of the internet big corporations DO love!
Sent from my SGH-I927 using xda app-developers app
You have a really good point, would save them a lot of money. Wouldn't surprise me either if that's what they did. Either way, I'm not updating to official release when its available again anyway.
sent from my captivate glide running ICS (NardROM 0.4 Rooted)
The LH2 build was released as the official ICS update on September 7 but was pulled out a week later. Samsung even took out their upgrade instructions, replaced with a message telling users the update has been put on hold. I know at xda-developers we can find workarounds for almost any bug, including the broken keyboard lights on the LH2 update but the truth is not everybody comes to xda-developers and/or is comfortable with custom flashing.
I couldn't resist the urge to write both Samsung and AT&T about this update. Can you imagine them releasing an update for the Galaxy Note where the stylus doesn't work? Well, as a software tester myself (that's how I make a living though not in the mobile field), I couldn't believe something as basic and essential to the Captivate Glide's reason for existence as is sliding open the keyboard and checking out the backlight, could slip through the cracks both at Samsung and at AT&T. I was especially harsh with the people at AT&T when I wrote to them. If AT&T gets a software build that does not block free tethering, or doesn't have the requested bloatware or doesn't make it so said bloatware can't be uninstalled by the user, AT&T would have rejected the build and make Samsung fix the software. But it was way too taxing on AT&T's software testing schedule to slide open the keyboard and notice that the backlight wasn't working.
The sad part is, a tester probably did report the problem and yet some genius in upper management decided to release the software after all.
It is likely it was not tested on the Glide besides booting it to make sure it worked. The code for the keyboard backlight isn't just buggy, _it doesn't exist_. They clearly just compiled something for a similar model, such as the Gaalxy R and then called it good.
Sent from my SGH-I927 using xda premium
Big screw up on AT&T's part. I'm really surprised at Samsung for not at least noticing the backlight not working. Meh, I don't care honestly. CWM and XDA are all I need honestly.
sent from my captivate glide running ICS (NardROM 0.4 Rooted)
I have to say i really agree with Evil Alex. Many of us have been anxious and very excited to receive the update. I was holding off for an 'official' and it happened finally but I was pretty butthurt over the lack of the light up keyboard when i was walking down the street at 10pm and couldn't see my buttons! I'm unable to contribute yet so I'm just being patient and figure I'll await for XDA pros to muster up some new custom roms from the leak, or even eventually an official. With the troubles i'm having with ICS even after wiping everything, I guess i'll eat gingerbead again for a while