So I have this problem where when I am running Cyanogen Mod (currently 128 of ICS) on an R800x and the data will randomly just stop working, and the only way to fix it is to reboot the phone. Everything else appears to be working perfectly. I am running the latest firmware from that stickied thread in the developer's section. Any ideas why this is happening and how i can fix it? Btw as far as I can tell it's only the data that stops working, not sending/receiving calls/texts or wifi.
xrishox said:
So I have this problem where when I am running Cyanogen Mod (currently 128 of ICS) on an R800x and the data will randomly just stop working, and the only way to fix it is to reboot the phone. Everything else appears to be working perfectly. I am running the latest firmware from that stickied thread in the developer's section. Any ideas why this is happening and how i can fix it? Btw as far as I can tell it's only the data that stops working, not sending/receiving calls/texts or wifi.
Click to expand...
Click to collapse
Yeah, It's like that with all us cdma users. I've brought it up and fxp doesn't even acknowledge it. All you need to do is turn the mobile data off then on again. It's annoying, but until a decent dev looks into it it's the only workaround
ive tried putting it into airplane mode, and taking it back out, but that doesn't fix the problem. how do you do it?
and is there a way we can politely point this out to them, without acting completely entitled? like if its effecting all cdma users that's a pretty large group.
xrishox said:
ive tried putting it into airplane mode, and taking it back out, but that doesn't fix the problem. how do you do it?
and is there a way we can politely point this out to them, without acting completely entitled? like if its effecting all cdma users that's a pretty large group.
Click to expand...
Click to collapse
Well nobody on the fxp team has an r800x, I think two of them have gsm versions. So they can't test it out, and with my history with fxp himself he doesn't seem to really care about cdma at all (doesn't least show he does). People have mentioned it before and nothing comes from it. So it's a lack of caring about our type of issues, they don't have time, or it's beyond their comprehension. Your best bet is to mention it to Pax, since he does a lot of things for cdma. Here's a link to his profile
http://forum.xda-developers.com/member.php?u=4234200
Here is Keiran's profile also (he's on the fxp team)
http://forum.xda-developers.com/member.php?u=4344506
Oh, and the way I do it is: setttings>more..>mobile networks> Check data enabled off (wait 5sec) then check it back on. If that doesn't help then you can try a fresh install to see if it does anything
agraceful said:
Well nobody on the fxp team has an r800x, I think two of them have gsm versions. So they can't test it out, and with my history with fxp himself he doesn't seem to really care about cdma at all (doesn't least show he does). People have mentioned it before and nothing comes from it. So it's a lack of caring about our type of issues, they don't have time, or it's beyond their comprehension. Your best bet is to mention it to Pax, since he does a lot of things for cdma. Here's a link to his profile
http://forum.xda-developers.com/member.php?u=4234200
Here is Keiran's profile also (he's on the fxp team)
http://forum.xda-developers.com/member.php?u=4344506
Oh, and the way I do it is: setttings>more..>mobile networks> Check data enabled off (wait 5sec) then check it back on. If that doesn't help then you can try a fresh install to see if it does anything
Click to expand...
Click to collapse
thanks for the quick fix. worst case scenario that isn't too inconvenient of a fix. i tried sending both of them a polite message, and we'll see if anything comes of it, though probably not.
Hey,
Although I'm not on FXP team anymore (working with AOKP now <3 unicorns haha) I looked into this issue once.
Any AOSP based ROM (CM, AOKP) for zeus and zeusc use prebuilt radio interface layer libraries, which is a problem, because the ones we are using in CM9 are gingerbread, not made for ICS.
I tried reverse engineering it once but I seriously need to work more on that kinda stuff
I'll tell jerpelea (FXP) of this issue and what he wants to do about it, its not really in my power now. Although if I do find a fix then I will be sure to push it to gerrit, regardless of FXP's opinion on the issue.
J is the only one I know with an R800x (he has whole 2011 line + S + P + x10)
Hope I could be of any help,
Keiran
KeiranFTW said:
Hey,
Although I'm not on FXP team anymore (working with AOKP now <3 unicorns haha) I looked into this issue once.
Any AOSP based ROM (CM, AOKP) for zeus and zeusc use prebuilt radio interface layer libraries, which is a problem, because the ones we are using in CM9 are gingerbread, not made for ICS.
I tried reverse engineering it once but I seriously need to work more on that kinda stuff
I'll tell jerpelea (FXP) of this issue and what he wants to do about it, its not really in my power now. Although if I do find a fix then I will be sure to push it to gerrit, regardless of FXP's opinion on the issue.
J is the only one I know with an R800x (he has whole 2011 line + S + P + x10)
Hope I could be of any help,
Keiran
Click to expand...
Click to collapse
Ah ok I can see the issue now, I honestly never even considered that. I deved on gb for many years and I'm still not use to ics yet lol. I seriously thank you for responding. From what I can tell gsm users don't have this issue (maybe they do but the ones I've talked to don't) and even though it's not major to me it'd be nice to be on the same level you know? Since you're on aokp I may jump onto that soon, but thanks again Keiran, I hope you stick with developing you got a knack for it that most people don't.
Related
Hi all,
Just recently flashed the new FXP123 build and the newest CM9 nightly. I am having an issue with both. As some may or may not know, the new FXP123 build came with a new kernel. This new kernel doesn't allow overclocking and seems a little sluggish.
My solution was to flash a different ICS kernel (KeICS v2, Darkforest v5, DooMKernel v3). Upon flashing a different kernel, WiFi would be broken. When I would attempt to turn it on, it just stays at "Turning Wi-Fi on..." indefinitely. When I reflashed the new FXP123 kernel, WiFi would be restored.
Are these new CM9 builds not compatible with other kernels? It seems odd that both FXP and the new CM9 nightly both have this issue. I've tried flashing the kernel before and after wiping data for a new ROM install, wiping after flashing, etc. I've tried using the different command in fastboot (fastboot -i 0x0fce flash boot <boot>.img). Nothing has worked.
Apparently FXP has changed the way wifi modules are loaded pax has said. Guess we just need updated kernels or patches. Solved?
Sent from my R800x using Tapatalk 2
Sluggish doesnt even begin to describe my experience with FXP123. It's my first time using CM9 so I can't compare it to previous builds, but holy crap is it slow.
Coming from CM7, I expected a small hit to performance but not to this extent. Everything takes 2-3 times longer to load or react on CM9 compared to CM7.
I hope this is just a problem with FXP123.
3dawg said:
Sluggish doesnt even begin to describe my experience with FXP123. It's my first time using CM9 so I can't compare it to previous builds, but holy crap is it slow.
Coming from CM7, I expected a small hit to performance but not to this extent. Everything takes 2-3 times longer to load or react on CM9 compared to CM7.
I hope this is just a problem with FXP123.
Click to expand...
Click to collapse
Try Aokp, it's latest build is based on fxp123 and is running smoothly without over clock, although I only have a few apps installed to prevent sluggishness
Sent from my Xperia Play using XDA
Nabeel_Nabs said:
Try Aokp, it's latest build is based on fxp123 and is running smoothly without over clock, although I only have a few apps installed to prevent sluggishness
Sent from my Xperia Play using XDA
Click to expand...
Click to collapse
I really love CyanogenMod and after seeing the behaviour of some AOKP devs, I'd rather not support them.
http://www.reddit.com/r/Android/comments/uj5bc/dont_bother_reporting_bugs_to_the_aokp_team_they/
Unfortunately the chat log was deleted but I'm sure if you dig into the comments, people have logs.
EDIT: I understand this is an unofficial AOKP port for the PLAY and is not developed by the assholes in the provided link (the same asshole who essentially stole a HP Touchpad and HTC resound from the dev community) , perhaps I should leave my prejudices at the door and try it.
3dawg said:
I really love CyanogenMod and after seeing the behaviour of some AOKP devs, I'd rather not support them.
http://www.reddit.com/r/Android/comments/uj5bc/dont_bother_reporting_bugs_to_the_aokp_team_they/
Unfortunately the chat log was deleted but I'm sure if you dig into the comments, people have logs.
EDIT: I understand this is an unofficial AOKP port for the PLAY and is not developed by the assholes in the provided link (the same asshole who essentially stole a HP Touchpad and HTC resound from the dev community) , perhaps I should leave my prejudices at the door and try it.
Click to expand...
Click to collapse
I agree with trying it don't let the conduct of one or two of them take away from romans amazing talent. And as you said it's unofficial, so support our devs here.
Sent from my R800x using Tapatalk 2
Pax will be releasing new ROMs and Kernals shortly I believe that hold the old WiFi modules which should work for you guys. But noticed since I flashed the last kernal provided by FXP I have seen massivve improvement. Litrally my phone was on 30% battery. Put my phone next to my bed and today morning woke up seeing the battery was only down to 25 percent. So then I put it in charge and in 1 hour I see the phone's led is green indicating fully charged and surprizingly enough it was fully charged.
I have been looking for a couple of weeks, but I can't find anything that is just this. I don't know much about development, so I wouldn't know how to take what someone else has done and modify it to how I want.
Basically, I am wanting a Paranoid Android soft key area. I want to get rid of the nav bar up top and move my clock, battery, signal, wifi, etc. to the bottom with the soft keys. That is the only change I really want to make.
I know that this is one of the premier features of Paranoid Android, but it is my understanding that PA for JB is based on CM10 and still has a lot of bugs to flesh out, especially on the CDMA/Toro version. Also, I do not know enough to figure out the tablet mode, hybrid mode, and regular mode stuff, especially since some of it is done in ADB (again, my understanding of it, I could be wrong).
Is it possible to do only what I described without flashing to PA for JB? I feel like some of the modifications I have seen posted in this forum come close to this, but the ones I remember off the top of my head move only the clock to the bottom.
Thanks to anyone who can help.
May I ask, why you dont want to flash PA? what bugs are keeping you from flashing?
I am currently running it and there are no real bugs, that irritate me (I dont use bluetooth^^)
And since a new build will be coming very soon even the toro devices should be fine aswell.
Nordpolcamper said:
May I ask, why you dont want to flash PA? what bugs are keeping you from flashing?
I am currently running it and there are no real bugs, that irritate me (I dont use bluetooth^^)
And since a new build will be coming very soon even the toro devices should be fine aswell.
Click to expand...
Click to collapse
I will definitely flash PA in the future, I would just prefer to wait until all the bugs are kicked.
First, I need to be able to be reached on my phone all day and by email (which I check 95% of on my phone) at all times. Apparently there is a problem with gmail on PA right now, as well as other smaller bugs. While I can't name any specifically that I remember, I do know the developer himself is calling it very alpha. While I love the developer-made ROMs, I also need stability, at least until the summer is over and I'm back in school.
Second, it is my understanding (I love that saying, obviously) that you have to do a full wipe each time you flash a new version of any CM-based ROM. Because I hate having to re-download and re-log into all of my apps (especially ones that need credit card numbers), I usually stay on stable ROMs that allow me to dirty flash when newer versions are released. I know there are ways around this, but I don't know enough to get around it at the moment nor do I have time to learn how to do it until school starts back up.
TexPP said:
I will definitely flash PA in the future, I would just prefer to wait until all the bugs are kicked.
First, I need to be able to be reached on my phone all day and by email (which I check 95% of on my phone) at all times. Apparently there is a problem with gmail on PA right now, as well as other smaller bugs. While I can't name any specifically that I remember, I do know the developer himself is calling it very alpha. While I love the developer-made ROMs, I also need stability, at least until the summer is over and I'm back in school.
Second, it is my understanding (I love that saying, obviously) that you have to do a full wipe each time you flash a new version of any CM-based ROM. Because I hate having to re-download and re-log into all of my apps (especially ones that need credit card numbers), I usually stay on stable ROMs that allow me to dirty flash when newer versions are released. I know there are ways around this, but I don't know enough to get around it at the moment nor do I have time to learn how to do it until school starts back up.
Click to expand...
Click to collapse
well that gmail issue is a myth^^ you can simply change the dpi to phone and everything works flawless
Furthermore moles said, that form 1.7 onwards you wont need a factory reset anymore^^
Nordpolcamper said:
well that gmail issue is a myth^^ you can simply change the dpi to phone and everything works flawless
Furthermore moles said, that form 1.7 onwards you wont need a factory reset anymore^^
Click to expand...
Click to collapse
Thanks for the info. I just sent you a PM regarding some of what I said, but I sent it before seeing this reply. I may try to jump on PA tonight if it is working better.
i am a super omega ultimate noob lv. -99. i am wondering how to check on the latest status of the GSIII stable roms. i would like to know if/when CM will get the roms first or if xda gets them first. i like stable roms because i am a noob. my noobness knows no bounds. please help. i do dontate. thank you.
Right now, CM10 nightly 25 is working great
26 has exhibited a few irritating bugs but I haven't had any problems with nightly 25
Give it a run, it's phenomenal IMO
o-k said:
i am a super omega ultimate noob lv. -99. i am wondering how to check on the latest status of the GSIII stable roms. i would like to know if/when CM will get the roms first or if xda gets them first. i like stable roms because i am a noob. my noobness knows no bounds. please help. i do dontate. thank you.
Click to expand...
Click to collapse
Xda is just an outlet where people choose to post roms.
To check on the latest status of roms, you need to open the threads and read the OP. You also need to spend at least ten minutes reading each thread, That will tell you how stable each rom is and what kind of results people are having.
Sent from my SGH-T999 using xda premium
Is there a place for specific roms that we can see a list of all known bugs? I've been trying to check on, for example, CM10, paranoid android, and AOKP in particular and havent been able to find any bug trackers at all. Without knowing what bugs there are and what will/wont affect me, I'm too hesitant to try any of the roms and have been suffering through t-mobile's dual "update ready" and "update needed" constant un-clearable notifications. I cant even apply the stock updates because I debloated and applying the update fails because I dont have the apps that the update is attempting to update. Updating would involve doing a full factory reset back to stock and THEN updating, which means i'm probably better off simply waiting for samsung's official JB update to roll out in the first place
shrimants said:
Is there a place for specific roms that we can see a list of all known bugs? I've been trying to check on, for example, CM10, paranoid android, and AOKP in particular and havent been able to find any bug trackers at all. Without knowing what bugs there are and what will/wont affect me, I'm too hesitant to try any of the roms and have been suffering through t-mobile's dual "update ready" and "update needed" constant un-clearable notifications. I cant even apply the stock updates because I debloated and applying the update fails because I dont have the apps that the update is attempting to update. Updating would involve doing a full factory reset back to stock and THEN updating, which means i'm probably better off simply waiting for samsung's official JB update to roll out in the first place
Click to expand...
Click to collapse
Actually that would be a great idea. It would help out the entire community.
Right now the way things exist, you pretty much have to read through an entire rom thread to determine the benefits/bugs of any given rom.
You could, for example, start a list for any particular rom.. read the entire thread, then make your own thread detailing current known bugs and post it in the same forum. Then the OP of the rom thread could post your link in the first post making it easy for everyone to find.
That would serve two purposes - you would learn the information you're seeking and also become an instantly appreciated contributor to the site.
Sent from my SGH-T999 using xda premium
I'm surprised the rom developers dont already have a system in place, though. The scope of the projects are presumably gargantuan collaborative works. i kind of assumed that they must have some sort of a bug tracking thing that they use between them. That bug tracking thing is what i've been venturing to find. There are a ton of user-specific bugs that I have no problem digging through the forums and figuring out myself, but what i'd love to see with roms is a list of "this is what we know isnt working yet. dont talk to us about this. we are working on it." or at the very least, "when you flash this rom, if you would like to help, run this command and upload the output HERE so we can fix some bugs we know about".
I'm coming from a linux world and it is very disconcerting to me to flash a rom, encounter a bug/error, and not be able to look at any sort of an error message or do anything to fix the problem except reboot/wipe/reflash and hope for the best. thats a very windows-y mentality to the whole thing, and i feel like if we're running linux on the phones we should be able to get a bit more involved in fixing our own problems a bit better too.
I guess what i'm trying to say is, i'd like to help and i have no clue where to even begin. with archlinux theres a beginners guide but with these roms its more of a "watch this youtube video and follow this tutorial but god help you if anyone thinks you are complaining about what people are doing for you for FREE".
EDIT: I found CM10's issue tracker, but there isnt anything specific for the GS3 there. The flicker and picasa sync issues arent even mentioned. Obviously Paranoid Android and Kang will have the same bugs as CM10, but im assuming that they'll have their own bugs introduced after they add in their own features and such.
ok.
ingenious247 said:
Right now, CM10 nightly 25 is working great
26 has exhibited a few irritating bugs but I haven't had any problems with nightly 25
Give it a run, it's phenomenal IMO
Click to expand...
Click to collapse
thanks! will it be on the CM website or here?
o-k said:
thanks! will it be on the CM website or here?
Click to expand...
Click to collapse
Two things - one, if you're going to do a lot of flashing, and especially with CM10, you will want to install ROM Manager from the Google Play Store. It will make managing your updates/downloads easier
Two, there is a dedicated thread to CM10 in the "T-Mobile Galaxy S III Original Android Development" forum here:
http://forum.xda-developers.com/showthread.php?t=1778217
Read a lot first - before you do anything.. unless you are a very experienced user.
If you have specific questions I will be happy to help
i have a question
ingenious247 said:
Two things - one, if you're going to do a lot of flashing, and especially with CM10, you will want to install ROM Manager from the Google Play Store. It will make managing your updates/downloads easier
Two, there is a dedicated thread to CM10 in the "T-Mobile Galaxy S III Original Android Development" forum here:
http://forum.xda-developers.com/showthread.php?t=1778217
Read a lot first - before you do anything.. unless you are a very experienced user.
If you have specific questions I will be happy to help
Click to expand...
Click to collapse
i've downloaded the CWM pro and the TB pro. i was wondering what exact ROMS i can use. There is also the difficulty of understanding which rom is exactly which. Is there a way to view the Change log? i'm a super noob. i'm really sorry.
Changelogs won't do you much good.
I recommend flashing everything through CWM (make sure you have 6.0.1.2 Touch - in my signature if not). I wouldn't use ROM Manager at all. Having automated tools is great, but learning how to do it yourself is even better. Plus, if you break something, knowning what you are doing makes it easier to fix. Automated tools hurt more than they help.
As for roms, your options pretty much are as follows:
CyanogenMod: AOSP, the closest thing we have to the stock Google firmware.
AOKP: Pretty much CyanogenMod with some extra options. Nothing extraordinary about those extra options, just some nice things like center clock, swagger toggles, and unicorns.
MIUI: iPhone look for Android.
ParanoidAndroid: Scalable - for tablets (imo).
Then you have the neverending amount of customized stock (TouchWiz) roms.
They are all under constant development. If you want "stable", stay on your stock firmware. All of the roms listed above are stable enough to use as a daily driver. They all have threads in the two Dev forums. But if you don't know what to pick, use CyanogenMod.
I still think ROM Manager is a great tool, it's how I started years ago and I still managed to learn what I needed to over time flashing manually
Sent from my SGH-T999 using xda premium
Andromadus - Test Builds
To start with here you will find test versions of ROMs built by me from the Andromadus github repo http://github.com/Andromadus, think of them along the same concept as nightly builds just not every night These are development ROM's, if you want to run bleeding edge development ROM's and at least know how to use adb and logcat then you might find something of interest here. If you require something that works 100% of the time all of the time then this might not be for you. That said you can always give it a try and if it doesn't work restore your previous nandroid backup!
What IS Andromadus?
Initially it was a group of people who got together to make ICS work on the HTC Desire Z because nobody else seemed to want to support devices with physical hardware keyboards/trackpads. Whilst the idea stays the same It has grown slightly to support some other hardware and some of the work we have done is now used in many other devices. Andromadus builds of CM10 or CM10.1 are basically CM sources with a few additional tweaks or additions to support our phones.
1. New versions will be added as and when I feel there are enough changes to warrant one, don’t ask when the next version is coming.
2. If we decide to release a "Stable" version of these roms they will be published in another Andromadus thread.
Direct all your queries with release versions to that thread and in the same vain do not discuss these releases anywhere but here.
3. I will do as best I can to answer questions but if you don't get an answer from me I'm sure somebody else will be along to help. Help each other and I have more time to spend fixing things!
4. Don't ask for what's changed since the previous version, have a look at the recent submits on the Andromadus github if you want to know or wait for the mini changelogs when I post a new release.
5. If there is something in particular to test it'll be mentioned!
6. As always if you didn't wipe between installations then at least verify that the problem exists on a clean install before posting here. Nandroid/superwipe/install/check at the end of the day you can always restore your nandroid if the problem is reproducible on a clean installation. If you can't be bothered to try this then I really can't be bothered to try to help you :>
7. All that said ensure you make a nandroid/backup before hand. I take no responsibility for what you do to your phone with these ROM.
8. Whilst I can't stop you I would rather these builds were not used as a base for any ROM/MOD/ETC. The source is all available if you want to do your own builds with which you can do whatever you like.
9. Tell us what works/what's worse/what's better but don't ***** when something breaks or isn't fixed yet, report it and move on.
10. Sometimes people forget that we do this for fun, for ourselves, and sometimes your super important issue is way down on our personal list of things to be fixed.
If you ignore any of the above you will in turn be ignored.
Now that's all out of the way as always have fun
As usual you need to flash the ROM then GAPPS.
Checkout http://andromadus.flinny.org for links/files/changelog's
This a team/community effort, I'll not list everyone who has helped along the way here that list is in the beta thread but I will say thanks to all of them again and obviously anyone that has been missed.
Reserved
Hi Flinny, great job on the AOSP builds they are running perfect. I only had one satback sins build 4. Suddenly my gallery stopt working and dropbox to. Because of the gallery problem my camera won't boot either. I flashed build 5 but I had the same problem. Build 4 was flashed with a full wipe and build 5 was flashed as update that the reason of course why the problem didn't left but sometimes it helps Does this sound familiar? Greetz Munky
I tested it last evening but have many FC message about "aosp keyboard" even with the physical keyboard
I wiped all but still the same message going back to cm10.1
Ok I'm a little rusty on the details at the moment but: AOSP means that you want it to get as close as stock experience as you can get right? (I'm really looking for a G-lite thing but then with ICS/Jelly Bean, sort of Nexus feel but then for our Desire Z)
What's everyone's opinion on these AOSP builds? To me they seem more stable and faster than CM. I kinda miss CM a little though, but not the lag.
Sent from my HTC Vision using xda app-developers app
I know that this is a dumb question and the answer is probably within the other thread, but... Ah heck, now it's just that I'm too lazy to look for the solution LOL...
But I installed AOSP 4.2 v6 last night and so far I'm not experiencing any major problems (except for FCing when I edit a picture and a bit of confusion adjusting to some new features LOL)... But when is this project going to be merged with CM? There are LOTS of creature comforts (e.g. silence during night hours, T9-style contact search, etc.) that I'm used to with the CM-optimized version that I kinda miss and only noticed that it was gone when I flashed it (I was under the impression that those features were all standard?)
Sorry to pester and thanks in advance.
EdWaRdW818:
Here you've got CM10.1 which is based on AOSP 4.2
http://forum.xda-developers.com/showthread.php?t=2031678
Flinny:
Could you add init.d support to the rom or fix it? I see that there is a placeholder for scripts and there is one script, but it's not executed on boot (with 755 permissions).
Eddy130306 said:
What's everyone's opinion on these AOSP builds? To me they seem more stable and faster than CM. I kinda miss CM a little though, but not the lag.
Click to expand...
Click to collapse
Have you tried Flinny's CM 10.1?
(I haven't - I'm just curious as to what you think)
google ears
EDIT: Sorry wrong thread
BTW: how can I delete my post?
I can't find changelog in your site flinny can you link it ?!
Inviato dal mio HTC Vision con Tapatalk 2
zofox said:
I can't find changelog in your site flinny can you link it ?!
Inviato dal mio HTC Vision con Tapatalk 2
Click to expand...
Click to collapse
http://andromadus.flinny.org/?q=node/2
This is absolutely the smoothest 4.0+ ROM I have ever used. Might switch to CM10.1 though for more features.
adamz667 said:
EdWaRdW818:
Here you've got CM10.1 which is based on AOSP 4.2
http://forum.xda-developers.com/showthread.php?t=2031678
Flinny:
Could you add init.d support to the rom or fix it? I see that there is a placeholder for scripts and there is one script, but it's not executed on boot (with 755 permissions).
Click to expand...
Click to collapse
catachresistant said:
Have you tried Flinny's CM 10.1?
(I haven't - I'm just curious as to what you think)
Click to expand...
Click to collapse
Oh jeez... Either I had a total brain fart and completely missed the link or it got posted anywhere from the time I posted it to the catching up of 14+ hours of sleep (I only slept 7 hours across 3 days LOL), but I guess CM10.1 is already posted. I'll download it and see what's up. Thanks for not flaming me guys. I would've gotten the N4 but I'm not a big fan of LG (had countless bad hardware experiences) and my phone is somewhat last on my "to upgrade list", so thanks for everybody's help and keep up the good work! There's some top quality Münchner Bier mit your name on it once I get some disposable income
catachresistant said:
Have you tried Flinny's CM 10.1?
(I haven't - I'm just curious as to what you think)
Click to expand...
Click to collapse
No I have not.
Sent from my HTC Vision using xda app-developers app
---------- Post added at 02:11 PM ---------- Previous post was at 02:00 PM ----------
LAMER_CZ
That is strange. Which recovery are you using? Don't use clockworkmod as they're always full of glitches and bugs. Don't use ROM Manager to flash ROMs either as they as well have glitches. I recommend doing everything in recovery. If you do have clockworkmod I recommend flashing 4ext as it has more features and can make your phone a little faster
Sent from my HTC Vision using xda app-developers app
Ok I just went ahead and installed it. This is exactly what I need for a ROM on my Desire Z! Thanks Flinny, and keep up the good work!
Now my experience with this ROM:
- I just fly trough my home screens and menu's, it runs fluently!
- When at stock speeds (so 1Ghz) I sometime run into problems booting up the settings. I just hangs there for 4+ seconds untill it actually shows the settings. Setting clockspeeds to 1,8Ghz fixes this most of the times, but it's something you might want to look into (Or don't, it's your ROM)
- The above also happens with some apps.
I don't run swap or any other optimization, so I don't know if it's my problem or a ROM problem, but if you want me to do some more testing just tell me what I need to do
Boot Loop
Thanks for the work, this is a great ROM, just thought I would pitch my issue I had.
Im currently testing an app and set the device to use 2g only as I wanted so see how quickly it pulled in my data on a slower connection. If you leave it in 2g mode and reboot it appears to get stuck in a boot loop.
Hope this is helpful.
Cheers
usc911 said:
Thanks for the work, this is a great ROM, just thought I would pitch my issue I had.
Im currently testing an app and set the device to use 2g only as I wanted so see how quickly it pulled in my data on a slower connection. If you leave it in 2g mode and reboot it appears to get stuck in a boot loop.
Hope this is helpful.
Cheers
Click to expand...
Click to collapse
I doubt that has anything to do with the "2g" setting since the radio doesn't come on until after it is booted up. Maybe that application you're testing screwed something up?
Authorita said:
I doubt that has anything to do with the "2g" setting since the radio doesn't come on until after it is booted up. Maybe that application you're testing screwed something up?
Click to expand...
Click to collapse
The app is fine, I have been building it for a few weeks and runds fine on a nexus one, and a sapphire. I have tried flashing the 4.2.1 AOSP build and the CM10 build and exactly the same is happening.
Guess I'm just missing something :s
usc911 said:
The app is fine, I have been building it for a few weeks and runds fine on a nexus one, and a sapphire. I have tried flashing the 4.2.1 AOSP build and the CM10 build and exactly the same is happening.
Guess I'm just missing something :s
Click to expand...
Click to collapse
Do you think you could get a log of the reboot? Might help in figuring out why it is rebooting like that.
Hey there!
i'm pretty new to modding android and recently got an A101 from a colleague - i think still one of the two best devices in the 7" format with only the Huawei Medipad providing the same functionality.
Anyway, i'd love to try something new and am already rooted with ZeroNull's method wich worked like a charm. Now that i've read many threads in this forum the past week i'm a little bit concerned about some things. First of all, when i'm in stock recovery my power button isn't working, so i cannot make any input besides selecting the menu-entries. Is it likely the case, that i would be facing this issue when installing a custom recovery? Since TWRP has a touch gui i shoudn't be aware of this, right?
Further A101 specific questions i wanne be 100% sure of, since there's no A101-Forum:
- i'm fine with installing bootloaders like TWRP or CWM made for the A100?
- aswell ZeroNull's unlock bootloader method?
- which custom ROM's do support 3G? I'm thinking about pio_masaki's Jellytime Sosei, his CM10 build, or KEBBERSROM...(?)
rather an ubuntu related question:
Am i fine with installing the packages: android-tools-adb & android-tools-fastboot or do i need the full - Android-SDK?
The most important thing for me is to get rid of acers bloadware, so i'm planning to install TWRP followed by a nandroid backup and kiling them softly *fingerscrossed*
running StockRom: Acer_AV0141_A101_1.015.00EMEA_DE
VolkerPfosten said:
Hey there!
i'm pretty new to modding android and recently got an A101 from a colleague - i think still one of the two best devices in the 7" format with only the Huawei Medipad providing the same functionality.
Anyway, i'd love to try something new and am already rooted with ZeroNull's method wich worked like a charm. Now that i've read many threads in this forum the past week i'm a little bit concerned about some things. First of all, when i'm in stock recovery my power button isn't working, so i cannot make any input besides selecting the menu-entries. Is it likely the case, that i would be facing this issue when installing a custom recovery? Since TWRP has a touch gui i shoudn't be aware of this, right?
Further A101 specific questions i wanne be 100% sure of, since there's no A101-Forum:
- i'm fine with installing bootloaders like TWRP or CWM made for the A100?
- aswell ZeroNull's unlock bootloader method?
- which custom ROM's do support 3G? I'm thinking about pio_masaki's Jellytime Sosei, his CM10 build, or KEBBERSROM...(?)
rather an ubuntu related question:
Am i fine with installing the packages: android-tools-adb & android-tools-fastboot or do i need the full - Android-SDK?
The most important thing for me is to get rid of acers bloadware, so i'm planning to install TWRP followed by a nandroid backup and kiling them softly *fingerscrossed*
running StockRom: Acer_AV0141_A101_1.015.00EMEA_DE
Click to expand...
Click to collapse
Cwm and twrp are recoveries, not boot loaders, and are fine for the 101, no worries there. Everything for the a100 works for the 101 except the Roms, a100 ROMs on a101 kills 3g. You lose 3g, period. Cm10.1 I had some experimental 3g stuff in there but I never heard back on that.
Maybe I'll see about adding it to cm10.
Sent from my HTC DNA
pio_masaki said:
Cwm and twrp are recoveries, not boot loaders, and are fine for the 101, no worries there. Everything for the a100 works for the 101 except the Roms, a100 ROMs on a101 kills 3g. You lose 3g, period. Cm10.1 I had some experimental 3g stuff in there but I never heard back on that.
Maybe I'll see about adding it to cm10.
Sent from my HTC DNA
Click to expand...
Click to collapse
Thats too bad to hear but i was expecting this. Just thaught that CM10 could have 3G functionality since some friends are using cyanogen on their phones. And since Sosei lacks of GPS it's not an alternative for me either. After all i convinced my wife to buy the a101, so that we can use it as navigation aswell ;P
well well, i really would appreciate the 3G Feature in your CM10, but i dont wanne hassle so - just if you have time for it of cause.
greetings and thanks so far
VolkerPfosten said:
Thats too bad to hear but i was expecting this. Just thaught that CM10 could have 3G functionality since some friends are using cyanogen on their phones. And since Sosei lacks of GPS it's not an alternative for me either. After all i convinced my wife to buy the a101, so that we can use it as navigation aswell ;P
well well, i really would appreciate the 3G Feature in your CM10, but i dont wanne hassle so - just if you have time for it of cause.
greetings and thanks so far
Click to expand...
Click to collapse
It can have 3g just fine, I've asked a few times for the 3g ril files from 101 users wanting me to build for them, they always vanish and I never hear back about it.
A100 just had its rotation for builds last night / this morning so it'll come up again sometime between wed-fri I think. Been looking at updating the black bean build and maybe adding AOKP as well, I'll use them for testbeds. I may go ahead and just do an extra day on the A100 and see about getting a potential 3g build up for you.
Side note, sosei will use gps if you use the newer cm10 boot.img.
Current rotation is:
Nexus 7 holds priority as I've been invited to Team Sorcery as their N7 dev.
Toshiba Thrive 4.2 development, 4.1.2 updates and kernel work (voodoo sound) comes second as they've been extremely generous to me.
Droid DNA aosp porting as the device was pretty much donated
Slight GNex work as needed, rare
A100 is bottom/last as I don't own one, luckily fixes from the thrive usually directly move over to the A100
Other devices I don't own.
I have a few things planned for the A100 for some nice updates and releases to jeep you guys in a variety of ROMs, like AOKP and some updates to the cm9 kernel I use.
Sent from my Nexus 7 - JBSourcery 4.5
pio_masaki said:
It can have 3g just fine, I've asked a few times for the 3g ril files from 101 users wanting me to build for them, they always vanish and I never hear back about it.
A100 just had its rotation for builds last night / this morning so it'll come up again sometime between wed-fri I think. Been looking at updating the black bean build and maybe adding AOKP as well, I'll use them for testbeds. I may go ahead and just do an extra day on the A100 and see about getting a potential 3g build up for you.
Side note, sosei will use gps if you use the newer cm10 boot.img.
Current rotation is:
Nexus 7 holds priority as I've been invited to Team Sorcery as their N7 dev.
Toshiba Thrive 4.2 development, 4.1.2 updates and kernel work (voodoo sound) comes second as they've been extremely generous to me.
Droid DNA aosp porting as the device was pretty much donated
Slight GNex work as needed, rare
A100 is bottom/last as I don't own one, luckily fixes from the thrive usually directly move over to the A100
Other devices I don't own.
I have a few things planned for the A100 for some nice updates and releases to jeep you guys in a variety of ROMs, like AOKP and some updates to the cm9 kernel I use.
Sent from my Nexus 7 - JBSourcery 4.5
Click to expand...
Click to collapse
thats of cause comprehensible, since these iconias are quite old, right. And if i didnt needed the (3g)/hdmi (looking forward for ubuntu for android) i guess i would have baught an Nexus 7 aswell. However, in two weeks i got an exam and i'm investing way too much time right now in reading about all that stuff here so if you could direct me were to read about this 3g ril files or tell me how i can find them on the mashine i'll send it to you. I've read something about the build.prob but no mentions about 3g, cellular or ril or whatsoever in it. Also a "find" gave me nothing.
Unfortunately i have to read some annoying §&"/%§ now but i've set up the email notification now.
greetings