Since I am a newbe I can't post in the dev fourms so I will ask my question here. I sucessfully installed [DEV][CRACKFLASHERS] 4.1 Jelly Bean JRN84D (Gnex)/ JRN84C (SDK) with the WIFI update-crespo-JRN83C-preview-2012063001 but no audio is there a workaround a driver perhaps anything, I like this rom it's super fast on my Nexus S
Chris
This wouldn't belong in development anyway (starting new threads in development is for DEVS ONLY) so it's good you couldn't post there.
If you want everything working you should stay away from SDK ports. It's not what you want to hear but it's the truth. There is no source code to work from so they are often very wonky.
No, there is no audio. You have installed the latest port.
There will not be any audio fix for the port. We will have to wait for the Update from Google.
Sent from my Nexus S using xda premium
You should have read and asked around before flashing this ROM, as the previous users said and I would like to re-inforce this; SDK ROMs lack a lot of things and are not stable at all. They are not recommended, and they are basically good for previews and stuffing around.
If you really want the new Jelly Bean 4.1, then just wait a week or 2 and a stable version will come out, a custom ROM too.
If you want to revert back to a Custom ROM for now I suggest you use AOKP. It's very stable, reliable and easy to use. Make sure you don't flash a Stock ROM as this can cause problems.
Cheers
From what ive seen there is not audio yet. Devs are working hard to get it out and i appreciate it very much. :laugh:
Related
Hi, I have recently rooted my Desire S, with revolutionary, clockwork etc, and I currently ported this rom HTC_DESIRE_S_2.3.5-2.10.401.4.zip
Everything is working just fine, but theoretically, when I decide to port a new rom, how would I know which will work, and which won't?
Actually, I'm waiting until ICS is released for desire s, so I can find it and install it...
Are there any methods to identify which rom would be compatible?
Thank you!
kostistheo said:
Hi, I have recently rooted my Desire S, with revolutionary, clockwork etc, and I currently ported this rom HTC_DESIRE_S_2.3.5-2.10.401.4.zip
Everything is working just fine, but theoretically, when I decide to port a new rom, how would I know which will work, and which won't?
Actually, I'm waiting until ICS is released for desire s, so I can find it and install it...
Are there any methods to identify which rom would be compatible?
Thank you!
Click to expand...
Click to collapse
hey mate
your're actually talking about two different things: porting a ROM and flashing a ROM.
Porting means, you take a ROM from another device and modify it so it works on your device too.
flashing means, you take a ROM which is already optimized for your device
and install it, so you wipe the stock firmware and get a custom rom.
which of the two things is what you want to do? i think its just the flashing.
so you can take any ROM from the "development section", and if you follow the guides that you can find everywhere here im sure you will be succesfull and happy with it.
bytheway
there is no "best" ROM for your device. it all depends on what you need and want. there are alot sense 3.5 Roms, Endymion 3.4 is the one i would recommend. you can also try AOSP ROMs (android open source project, means no sense), cyanogenmod7 could be a good first choice. and you can also try ics right now, since there are at least 3 (?) ICS AOSP ROMs right now:
CM9, Virtuous Quattro RC3, IceColdSandwich
have fun!
Yes I meant "flashing" a rom
Thanks for all the information. That's the general idea I have as well, however I had this question because after I flashed another rom (official rom through htc sync - that could have been the problem) over my first flashed one , the phone was "bricked"....
kostistheo said:
Yes I meant "flashing" a rom
Thanks for all the information. That's the general idea I have as well, however I had this question because after I flashed another rom (official rom through htc sync - that could have been the problem) over my first flashed one , the phone was "bricked"....
Click to expand...
Click to collapse
i would never recommend to flash an official ROM over a custom ROM. But anyways, i think if you would have done a full wipe before flashing the official rom you wouldnt have got a "you call it brick"
a real "BRICK" is a useless phone, where there is no way to use it again.if there is still a way, its no brick.. but who cares about definitions
I recommend you to flash the ROMs only through recovery mode. AND ALWAYS DO A FULL WIPE BEFORE FLASHING A NEW ROM. very important
and dont forget to backup as always
Yes you are absolutely right. I'll have that in mind the next time I'll decide to flash a new one
Yeah the device wasn't completely useless, it hanged at boot...but I guess that was due to not following the right procedure as you previously described..
Thanks eyahl
Start flashing different roms and trying them for a day or two. First
Sens 3.0 and then sense 3.5 roms to see the difference. Only then you will know which rom is best for you.
+1 for Endymion 3.4,
+1 for Endymion
Swyped from my Desire S using XDA Premium
+1 Endymion
Sent from my HTC Desire S using xda premium
edymion, will try it
+1266592.23 for Endymion
kostistheo said:
Yes you are absolutely right. I'll have that in mind the next time I'll decide to flash a new one
Yeah the device wasn't completely useless, it hanged at boot...but I guess that was due to not following the right procedure as you previously described..
Thanks eyahl
Click to expand...
Click to collapse
Each ROM type suits different personal tastes, so there isn't an 'best' ROM for everyone. Trial and Error which ones suit you!
General opinions:
Stock
Pro: Straight from HTC, *newest kernel/drivers*, least likely to have compatibility issues.
Cons: HTC is slow to release updates, and sense interface is usually resource hungry.
Sense-like
Pro: usually keep the Sense interface, but custom kernals offer speed / various other improvements.Runnymead versions are kernals ported across from HTC Sensation (which offer some of the goodies like Beats Audio etc. that were not originally developed for Saga.
Cons: Sense interface is resource hungry...
CyanogenMod based
Pro: offer lots of customisations
Cons: not the most user friendly
AOSP
Pro: Roms from the android source, usually less resource hungry, so lighter and faster.
Cons: Obviously, no sense.
ICS Alpha/Beta
Not strictly a new category, but builds from the new Android 4.0 (ICS).
Currently some things (like camera) isn't fully working yet.
Note: new Desire S may suffer from camera/video lag bug with non-stock / non-sense ROMs, this is due to HTC putting in new hardware / driver into the new DS phones and the other kernels not reflecting this change yet.
Personally, I use SenseMOD Lite V1.2 build 2 as it is one of the few AOSP like builds that don't have the camera bug. Oxygen would have been best choice for me but unfortunately camera bug makes it unusable.
Hey guys. I don't want to drive over your feet, but I think the OP is already very satisfied with all those replies. specially the post above is really trying to help, but you spend much time to type what has already been written on the first page.
I appreciate your intend to help, bit I think the OP isn't gonna read this anymore..
Btw: endy!...
Sent by my fingers to your head
Hello respected Developers ,
Jelly Bean is released today with some new and important features. Nexus ROM is already available for download. Since Jelly Bean brings updated UI and few new features only it may be possible to port Nexus ROM.
Kindly consider its possibility and reply
Thank you all !
Here is direct download link
http://goo.im/roms/fabolous/maguro/bigxie_JRN84D_rooted_busybox_deodexed.zip
Hmm...so I was right. It can be ported.
Jelly Bean ported to HTC One X http://forum.xda-developers.com/showthread.php?t=1737736
I hope so.
I'm not a Developer, but I hope so :good:
nothing will be done until the source code is released (google said mid july)
Guys, chill. It is best we wait until ics is fully developed with the kernel 3.x before we talk about this. I am sure that this needs ICS as base. I have been researching about this jellybean update the whole day. it is somewhat a small update to the ICS with automatic widget resizing, GoogleVoice (commandable just like siri) and also less lag... this is just like a froyo to gingerbread update as they said in vid reviews.
now our future is on the 3.X kernel:good:
Hi
Did anyone noticed that kernel for jelly bean port on HTC one x.
It is 2.6.xxx
Sent from my GT-I9003 using Tapatalk
neil05 said:
@vishal
You are not the moderator in this forum. So don't act like a mod
Cheers:beer:
Click to expand...
Click to collapse
No, but I am
Thread moved and cleaned. Development section is only for roms/kernels, etc. being worked on with some kind of bootable image. This is not. (First hint was the title ends in a question mark)
Keep it polite guys.
---Jay--- From the Nexus
The porting Guide can be found here
http://forum.xda-developers.com/showthread.php?t=1739561
Thanks Jay
And apologies for posting in wrong section. Everyday we learn something new
Thanks !
Maybe...
I'm not a developer and i don't know how to port a ROM. However, I think porting an I9000 Jellybean Rom will be easier since I9000 and I9003 has similar specs.:laugh:
chung1213 said:
I'm not a developer and i don't know how to port a ROM. However, I think porting an I9000 Jellybean Rom will be easier since I9000 and I9003 has similar specs.:laugh:
Click to expand...
Click to collapse
an i9000 stock rom is impossible because samsung wont release one. and jb code is not out until mid-july. let's wait for cm10 to start
Sent from my Transformer Prime TF201 using xda app-developers app
NEXUS S got the jelleybean working
http://forum.xda-developers.com/showthread.php?t=1738756
Galaxy s are on there way to port jellybean.
Vasishta Reddy said:
NEXUS S got the jelleybean working
http://forum.xda-developers.com/showthread.php?t=1738756
Galaxy s are on there way to port jellybean.
Click to expand...
Click to collapse
i9003 will follow, once kernel 3.0 + ics is completely ported and good for day-to-day basis ^^
Everytime it happens that when we work on perticular version of cynogenmod then suddenly new version of galaxy device releases or new version of android releases then current development looks old to us. So we leave it in incomplete stage & we move forward to achieve new things of new cynogenmod but again everytime same story repeats & thats why we have so many incomplete cyanogenmod roms.
I want to suggest that if the developers are working on ICS cm9 then they must work on first to achieve kernel 3.0 & get stable cm9. People now should not rush to achieve JB leaving behing cm9 work incomplete. "One time one task"
vishal24387 said:
Everytime it happens that when we work on perticular version of cynogenmod then suddenly new version of galaxy device releases or new version of android releases then current development looks old to us. So we leave it in incomplete stage & we move forward to achieve new things of new cynogenmod but again everytime same story repeats & thats why we have so many incomplete cyanogenmod roms.
I want to suggest that if the developers are working on ICS cm9 then they must work on first to achieve kernel 3.0 & get stable cm9. People now should not rush to achieve JB leaving behing cm9 work incomplete. "One time one task"
Click to expand...
Click to collapse
K bro,why to waste time in partially working ports lets wait for source code's release .
Vasishta Reddy said:
K bro,why to waste time in partially working ports lets wait for source code's release .
Click to expand...
Click to collapse
Source code of jelly bean is of no use for us until we get kernel 3.0. Because building jelly bean rom or cm10 based on 2.x kernel is again a waste of time & again one more incomplete rom
vishal24387 said:
Source code of jelly bean is of no use for us until we get kernel 3.0. Because building jelly bean rom or cm10 based on 2.x kernel is again a waste of time & again one more incomplete rom
Click to expand...
Click to collapse
You're right on that one bro.
Regarding porting Jelly Bean, it's another challenge for our great developers. And it is possible since it has already started coming on many devices. Another point is that JB does not introduce System level changes like ICS but a major update over it. So JB should easier than ICS.
Regarding Incomplete ROMs, each and every developer has his own set of skills and can't do what other can do and we must respect this. What dhiru can do is not necessarily doable by others too. But this should not come as deterrent for some quality work like MIUI and AOKP. If we would have kept waiting for 'Perfect and Complete' ICS then we would never have these great ROMs. These guys are working within known limitations and doing a great job. So i would always encourage new challenges, innovations, ideas, development and ROMs. We again might have many things not working on JB Ports but that's what fuel the developers to take up challenge and win it. Remember the first ICS and MIUI Ports ? And look today Thankfully Lolation, Frank, UT36104, Vurrut did not get discouraged by current limitations and went on to port these great ROMs and fix bugs. Thank You guys
Take every new thing as a challenge and give your best with whatever you have in hand instead of crying of what's not there or what will come someday
Good Day guys
silentvisitor said:
Regarding porting Jelly Bean, it's another challenge for our great developers. And it is possible since it has already started coming on many devices. Another point is that JB does not introduce System level changes like ICS but a major update over it. So JB should easier than ICS.
Regarding Incomplete ROMs, each and every developer has his own set of skills and can't do what other can do and we must respect this. What dhiru can do is not necessarily doable by others too. But this should not come as deterrent for some quality work like MIUI and AOKP. If we would have kept waiting for 'Perfect and Complete' ICS then we would never have these great ROMs. These guys are working within known limitations and doing a great job. So i would always encourage new challenges, innovations, ideas, development and ROMs. We again might have many things not working on JB Ports but that's what fuel the developers to take up challenge and win it. Remember the first ICS and MIUI Ports ? And look today Thankfully Lolation, Frank, UT36104, Vurrut did not get discouraged by current limitations and went on to port these great ROMs and fix bugs. Thank You guys
Take every new thing as a challenge and give your best with whatever you have in hand instead of crying of what's not there or what will come someday
Good Day guys
Click to expand...
Click to collapse
I completely agree. People learn by doing hands on, and what I mean is building roms. Discouraging them just because you want them to complete a rom is very selfish, everybody has to start somewhere. Not everybody has sufficient knowledge in android programming to help with completing roms, i believe people feel a sense of accomplishment after building their first rom, only to be struck down by others that want a complete rom. I just want to say guys, don't discourage new roms please, think about other people's feelings. Thanks.
Cheers
Sent from my GT-I9003 using xda app-developers app
bscraze said:
I completely agree. People learn by doing hands on, and what I mean is building roms. Discouraging them just because you want them to complete a rom is very selfish, everybody has to start somewhere. Not everybody has sufficient knowledge in android programming to help with completing roms, i believe people feel a sense of accomplishment after building their first rom, only to be struck down by others that want a complete rom. I just want to say guys, don't discourage new roms please, think about other people's feelings. Thanks.
Cheers
Sent from my GT-I9003 using xda app-developers app
Click to expand...
Click to collapse
Its not about discouraging new rom development. Its about how well we concentrate on each thing to complete it. I am not saying that we should stuck to only one perticular rom development. But remember guys that google will not take a pause for us so that we can complete current cynogenmod rom. New versions of android will contineously come out by google but we must have to think whether we should run behind new roms or should we first build a base kernel 3.x without which every future development will remain incomplete...???
I got my new black verizon s3 yesterday and i love it, buttery smooth. I was coming from a HTC Thunderbolt. I had rooted my thunderbolt, however since rooting that phone, i noticed that data connectivity didnt seem to be as stable as the non rooted version of that phone.
Here is my question, do you guys recommend rooting this S3 phone? Has it effected the data connectivity (dropped signals, etc)? Some advice and direction for this new S3 user would be helpful from some of you all who have been S3 users for a while. Thank you!
I would recommend rooting since there is a lot of support for the device. Data should be fine but there have been some problems either user related mistakes or bugs in a ROM. Those problems are fixable. Most of the ROMs are stable even the 4.2 ROMs.
i rooted and i think its worth it. it is easy to do and pretty low risk. I did mainly because i wanted to under clock and get better battery life. I haven't noticed any issues regarding loss of data or anything. i run into some issues at times because i try different kernals and roms that are not 100% in their stable phase. But the act of rooting itself isn't going to cause you any issues.
thanks guys, i am going to root the phone tonight after work. i browsed thru the rooting instructions for the jellybean update software (which i got when i activated my phone). I just didnt want to run into unstable data connections like i had with my thunderbolt.
Can you guys recommend any good 4.1 Roms as well as 4.2 roms? Also what is the difference between android 4.1 & 4.2?
It depends on the ROM as all 4.2 ROMs as of now are AOSP ROMs while the 4.1 ROMs are either TW based or AOSP based.
TW is ok... better then Sense IMO, however I like the stock ASOP feel. I will give a 4.2 rom a try. can you recommend a popular, 100% working 4.2 ROM? I looked in the dev section and there are so many Roms to choose from........ 24 hours of having my S3 and i LOVE it! so buttery smooth!
Blackbean 7 Is the most stable of the bunch as of now.
Ok. If you are going to root and Rom there are some things you need to know.
Your going to want to unlock your boot loader. And make an imei backup incase you lose it during a flash.
Search those up and get them done and your good to go
Via my Google Galaxy S3 running magic beans
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
thanks guys, i rooted the phone with no problems last night. got root and unlocked bootloader. I wanted to try out CM10 so I fla**** it this morning. So far so good. really like 4.2
bsdesign0000 said:
thanks guys, i rooted the phone with no problems last night. got root and unlocked bootloader. I wanted to try out CM10 so I fla**** it this morning. So far so good. really like 4.2
Click to expand...
Click to collapse
Do you mean Cm 10.1? Because if you flashed cm10 you're still on 4.1. Cm10 has a stable release while cm10.1 is still on nightlies. I've been running 10.1 nightlies for about a month and have only noticed very minor issues. So minor I can't even remember what they are.
Words fails me. I am so disgusted I have ran out of expletives so I won't bother repeating them here. Seriously...voice dialer is STILL not working! This update was specifically designed to fix this bug and it is still not working. I just can't understand what is so hard about putting back in functionality that was working before in ICS and was necessary.
This is the sort of thing that gets people to switch over irrevocably to apple. This has been going on for like a year now. It is starting to feel like it is being done on purpose for God knows what reason. Does it work for anyone else?
android 4.2.2
i535VRBLK3
AOKP
What update? This phone is officially on 4.1.1 . You are not guaranteed anything by running custom software.
BattsNotIncld said:
What update? This phone is officially on 4.1.1 . You are not guaranteed anything by running custom software.
Click to expand...
Click to collapse
Fair enough. Although I never said I was guaranteed anything and apparently we are also not guaranteed to have important functionality (aka voice dialer) to work from one official release to the next. It worked fine when I had ICS it just broke when I was upgraded to JB. I would prefer not to have to root my phone to get it work, but if I waited for the official channels then I will likely have to wait until I get my next phone for a fix.
Both Google and AOKP mentioned that bluetooth issues were fixed with 4.2.2 and I was inquiring whether this worked for others as it did not work for me. Neither 4.1.1, nor 4.1.2 nor 4.2.1 nor 4.2.2 nor any of the other little hacks others have tried have worked and I know others on the official release of 4.2.2 for Nexus had similar problems so I was hoping someone might have run across a solution.
I know I sounded snarky, but I am just really frustrated.
So I do not know if this will help you but I had pacman rom and the dialer wasn't working so I reflashed, no wiping and it fixed it.
Also there is always the option of going back to the stable TW roms. Which is what I did. You can't be mad for things not running smooth when you're running custom roms that make no claims of stability.
Via my S3 CleanRom 5.6
CM-Freak said:
So I do not know if this will help you but I had pacman rom and the dialer wasn't working so I reflashed, no wiping and it fixed it.
Also there is always the option of going back to the stable TW roms. Which is what I did. You can't be mad for things not running smooth when you're running custom roms that make no claims of stability.
Via my S3 CleanRom 5.6
Click to expand...
Click to collapse
Thanks for the info, it was definitely worth a try. Alas the pacman rom did not do the trick. I had the official JB TW update and that is what broke my phone in the first place and I am not really interested in going back to ICS since I got the new phone so I can get Jelly Bean. I have also tried CleamROM and the the latest CM, AOKP and liquidSmooth 4.2.2 along with the just released gapps-jb-130301-signed.zip. No dice.
I'll keep banging away and let everyone know if I find a solution with other ROMs or tweaks.
I am not mad about custom ROMs not working properly I am mad about the official release breaking critical functionality for me.
I tried PK and PA ROMs in addition to aready mentioned. Voice dial does not work in any of them. I also tried Ktoonsez kernel - no dice. I think it's a major JB problem and there won't be any working ROM until Google fixes the issue. I just stopped trying :crying: ...
Question #1: GPS
I have the Samsung Galaxy S 4G which has been long rooted and I've installed a few roms now on it. Recently I upgraded to Revolt 4+ which is my first attempt to find a Jelly Bean ROM that will work for me. Well, I love it. Only problem is that it seems it doesn't have GPS? Google Maps work but Navigation doesn't follow me which I'm guessing means it's using internet to "find" me. There's no GPS flashing icons nor are there any settings for GPS. Is there anyway to get it working or is it just not working for this ROM?
Question #2: Aries?!
Many of the roms mention "Aries's common bugs" but google searching it gives me nothing. Where can I find information about Aries?
Question #3: The latest fully-working ROM?
There are soooo many ROMs to choose from for the SGS4G that I don't know what to look for. I found and have been using THIS page but not sure how outdated/accurate it is. Anybody know the best/most recommended ROM right now that has all the main parts working? GPS, WIFI...etc? I know wifi calling always has issues but not important.
:good: to anybody who is able to help with any of the above!
Hi.
#1 All JB ROMs (meaning 4.1.2 and above) have Aries kernel.
it is faster than Herrig kernel used before, and should be more stable, but, no developer was able to make GPS work with it. so, there's currently no JB ROM with a working GPS.
#2 If you want a working GPS you will need ICS (4.0.3/4.0.4) ROM :
CM9/AOKP/Slim/MIUI/Ultragen etc.
I'm a MIUI freak so I can say I love HebMIUI which is an upgraded MIUI version I came up with. you can try it (see my signature) or any of the others I mentioned.
Slight addendum to #1. Not entirely true. Some of the earlier JB ROMs were still Herring. The various 4.2 Wifi-bugs were on Herring. Any ROM where they tell you to do the 4.1.2 JB if you wanted Wifi, it's a Herring kernel. For that matter, I believe we've only had compiled 4.2.2 and above Aries here. So if the ROM is 4.1.2 JB, it's Herring. If it's 4.2.2 without working Wifi, it's probably Herring. If it's 4.2.2 with Wifi or 4.3, it's probably Aries.
Agree on ICS/GB for GPS though. HebMIUI or Ultragen 1.01 (DO NOT USE ULTRAGEN 1.00 AND POST BUG REPORTS) are probably your best ICS options.
THANK YOU both for clearing up alot of stuff for me. Thank you x2 for itzik2sh for recommending HebMIUI. I have it installed and I love it sofar. Hopefully somebody figures out JB GPS eventually.
I'll still check back here if anybody else has anything else to throw in.