Related
CM7.0.2.1....... sucks battery and app. Problems after update.... ??
Crans said:
CM7.0.2.1....... sucks battery and app. Problems after update.... ??
Click to expand...
Click to collapse
naw... running smooth as ever for me. maybe something went wrong with your install
Have you tried a different kernel? Make sure your screen brightness isn't up all the way also, big battery killer.
CM7 nightly
I dont think this belongs in development. try Q/A they might be able to help you out.
I am also having issues mainly with you tube all the videos are jittery as hell and tried a different rom and issue was gone.
Sent from my ADR6300 using XDA App
The difference. between 7.0.2 and 7.0.2.1 has been like night and day .....my batt. After taking off the charger today went from 100 to 95 in less that 10 seconds and I'm not getting fc's. But my display apps try and open than dissapear giving me no access...... I am running dual boot sooooo... that may be the cause but 7.0.2 worked great when I updated to it..... just didn't know if I was the only one
If its a well known major problem with development of a rom that is supposed to be stable than yes if no than Q/A with people whom aren't even rooted....... hmmmmm hard choice,I know it was for me....... please move this post if it's not in the right section...
You could check the threads for CM7 and see if it its a "development issue"...searching works from time to time
CM7 nightly
Just don't know why 7.0.2 to 7.0.2.1 would be so drastic.... understand nightlys but not stable
Crans said:
If its a well known major problem with development of a rom that is supposed to be stable than yes if no than Q/A with people whom aren't even rooted....... hmmmmm hard choice,I know it was for me....... please move this post if it's not in the right section...
Click to expand...
Click to collapse
Opening a new thread about a ROM rather than posting in that ROM's thread, running it in a non standard configuration, AND having an attitude when someone points out a Q doesn't belong in dev? Yeah, I see no problem at all. /sarcasm
You guys are getting sarcasm and straight forward confused thanks for any input that actually pertained to my question... to others.... think before you speak or ask ... done... Please close this thread ASAP
Crans said:
The difference. between 7.0.2 and 7.0.2.1 has been like night and day .....my batt. After taking off the charger today went from 100 to 95 in less that 10 seconds and I'm not getting fc's. But my display apps try and open than dissapear giving me no access...... I am running dual boot sooooo... that may be the cause but 7.0.2 worked great when I updated to it..... just didn't know if I was the only one
Click to expand...
Click to collapse
um, the only thing they fixed from .2 to .2.1 was the camera.
To many people here post issues that aren't from a clean wipe.
No issues, move along.
Thank you for your reply..... as stated before...done
Remove this Thread
Please remove this thread. We don't need the negativity. There are too many people spending they're own time to make CM7 what it is.
morrisdan said:
Please remove this thread. We don't need the negativity. There are too many people spending they're own time to make CM7 what it is.
Click to expand...
Click to collapse
Why, so people can go on downloading a supposed "stable" release only to find out it wasn't so "stable" to begin with?
I LOVE the CM crew and all they do for the scene, but I had a very terrible experience with 7.0.0 on the DINC. First it was jittery video (which I lived with for over a week) and then all my installed apps just suddenly quit working.
masully1984 said:
Have you tried a different kernel?
Click to expand...
Click to collapse
A "stable" ROM should never require an end user to try a different kernel.
Anyway, I ended up back on OMGB and couldn't be happier. The only FC I can find is due to installed software (Astro SMB Module).
I love using CM7 ... bugs or not please save your ignorance.morrisdan
Crans said:
If its a well known major problem with development of a rom that is supposed to be stable than yes if no than Q/A with people whom aren't even rooted....... hmmmmm hard choice,I know it was for me....... please move this post if it's not in the right section...
Click to expand...
Click to collapse
Just because someone posts something in Q&A doesn't mean they aren't rooted. Your attitude sucks man. My personal opinion would be to reflash and wipe I have been running the latest stable release for as long as its been out and been updating to the latest version asap and have had zero problems other than those cause by user error. Perhaps you did something. Gotta release 9/10 problems are user generated.
skyblaster said:
Why, so people can go on downloading a supposed "stable" release only to find out it wasn't so "stable" to begin with?
I LOVE the CM crew and all they do for the scene, but I had a very terrible experience with 7.0.0 on the DINC. First it was jittery video (which I lived with for over a week) and then all my installed apps just suddenly quit working.
A "stable" ROM should never require an end user to try a different kernel.
Anyway, I ended up back on OMGB and couldn't be happier. The only FC I can find is due to installed software (Astro SMB Module).
Click to expand...
Click to collapse
Dude you should always try different kernals with roms. You must be new. It is stable I've had zero problems. As stated previously 9/10s of problems are user error and with the ignorance you are displaying I'm gonna say you did something. Just a tip when you wipe you should multiple times becayse 3.X wipes like a dirty person.
cstrife999 said:
Dude you should always try different kernals with roms. You must be new.
Click to expand...
Click to collapse
Don't let my post count fool you. I've been around since the beginning with the G1. Final, Stable, these words suggest newbie usage. Final builds should come with a final kernel. Unless you're a dev, tester, or need something specific for a certain application then you shouldn't need to kernel hack.
cstrife999 said:
As stated previously 9/10s of problems are user error and with the ignorance you are displaying I'm gonna say you did something. Just a tip when you wipe you should multiple times becayse 3.X wipes like a dirty person.
Click to expand...
Click to collapse
I understand how memory wipes work, so I don't believe the multiple wipe requirement. However, if it is an issue with ClockworkMod 3.x then I do apologize for any nay say here against CM. However, that doesn't really explain why 7.0.2 and 7.0.2.1 came out so soon after 7.0.0, and I wasn't the only one with video troubles in 7.0.0.
/deleted
10char
Hey so I just recently started rooting and have experimented with a few ROMs and I really like Synergy a lot, but it has a lot to fix and I'm not understanding something. I see all over the place about Synergy nightlies but I don't see where I can get them? All I see is the download link from 7/17. I see the changelog that states that the locations settings issues were fixed on 7/19, but how do I get this? I see everyone talking about how great it is, and I agree but after a couple minutes it force closes every couple minutes and it unusable. What am I missing? Thanks
I couldn't tell you why the nightlies aren't posted BUT you may find something in the Synergy rom thread on page 204. I had the same question awhile back but then I stumbled onto that post. I haven't used the rom in weeks so idk about issues/solutions
You can find the ILLEGAL as HELL Synergy nightlies, which no novice user should be considering anyways, at infectedrom.com.
So strangely at 11:45pm last night my phone went absolutely nutty... Can't figure it out but all of my apps keep crashing. Gmail, Maps, etc.
I haven't updated CM7 since it came out months ago so I need a bit of help upgrading all of what needs to be done... I figure this is a good reason to bring things up to speed.
Ideally I'd like to get 7.1 on here. I also can't remember all of what I need to download to do this process. Not as brilliant as the rest of you!
Can anyone give me (or point me in the direction of) some step by step instructions of what I need to do? Real layman's terms...
Currently:
Android 2.3.3
Model number ADR6300
Kernel 2.6.37.6-incredikernel-gb-04192011+
CyanogenMod 7.0.0-Inc
Build Number GRI40
Help me get this puppy up and running!
Thanks all and Happy New Year!!!
Go to cyanogenmod.com and click on devices. Scroll down until you see the HTC Droid Incredible and click on it. Click on the wiki link. Everything you need to know will be there. Use the via clockworkmod recovery method.
Get 7.1 stable, the gapps for it, incredikernel ext4 and the adrenaline shot. That's should be good.
-My life is a shooting range, people never change-
I hate bad mouthing projects that people have worked so hard on. But, CM 7.x stable is NOT stable on the Dinc.
If you want to keep using CM 7.x (stable)...
expect this problem to keep happening. If you are a CM 7.x (stable) user and it hasn't happened to you yet, great. But, don't be surprised when it does. Yeah, check out the CM forum for 7.x stable on the Dinc... you will find many others who have the same problem (works great for some amount of time, and then constant FC's and freezes). I also just ran across another person in the Incredible discussion forum who had the same thing a few days ago. It happened to me after about a week on installing CM 7.1 stable, so I changed to Inc Deck (gingerbread) 1.3 stable. You can reinstall CM and it and it will work for some amount of time (completely unpredictable how long it will work). But someday, sometime...whammo... you will have useless phone, and you will need to reinstall again.
Some folks have said that the problem never goes away after a fresh install... I don't know about that. My phone screwed up, I searched and found many others with the problem, tried a quick fix, then abandoned CM 7.x stable immediately.
iowabeakster said:
I hate bad mouthing projects that people have worked so hard on. But, CM 7.x stable is NOT stable on the Dinc.
If you want to keep using CM 7.x (stable)...
expect this problem to keep happening. If you are a CM 7.x (stable) user and it hasn't happened to you yet, great. But, don't be surprised when it does. Yeah, check out the CM forum for 7.x stable on the Dinc... you will find many others who have the same problem (works great for some amount of time, and then is completely fubar'd). I also just ran across another person in the Incredible discussion forum who had the same thing a few days ago. It happened to me after about a week on installing CM 7.1 stable, so I changed to Inc Deck (gingerbread) 1.3 stable. You can reinstall CM and it and it will work for some amount of time (completely unpredictable how long it will work). But someday, sometime...whammo... you will have useless phone, and you will need to start over again.
Click to expand...
Click to collapse
Hmmm interesting. Out of all the roms I have tried for the droid Incredible, CM7 has by far been the most stable. Never had any trouble with it and I have, at times, used it for months before trying a different rom.
Oh I know! It seems to catch everyone off guard because it works fine for X number of weeks or months and then... FC and freeze hell!
A lot of the folks found it happened shortly after upgrading from 7.0 to 7.1. But just in the last couple of days I have run across a couple of people that were still using 7.0 and now seem to have the issue.
The guy at CM who does most everything for the Dinc seems to think it was related to a full /data/data partition. I reinstalled fresh and did the ext4 "no data limit" mod, after first having the issue, and it made no difference at all. So, I gave up on CM the same day.
CM7 nightlies have actually been my daily driver for most of my time having service on the Incredible.
I've heard the force close issues have been due to /data/data filling up. If you keep 20MB free or more you should be fine. Root explorer is one app that will list how much free is on /data/data and a recommended app for any rooted phone. the CM7 nigthly thread has a few suggestions on how to free space. Search not enough space on the nightlies thread.
Edit: I see you posted about the /data/data partition already.
Thanks for this tidbit... I haven't had the issue, nor do i plan on getting it.. I'm pretty adamant about keeping a certain percentage of free space on all partitions, so hopefully everything runs smooth.
Thanks again for the heads up.
tiny4579 said:
CM7 nightlies have actually been my daily driver for most of my time having service on the Incredible.
I've heard the force close issues have been due to /data/data filling up. If you keep 20MB free or more you should be fine. Root explorer is one app that will list how much free is on /data/data and a recommended app for any rooted phone. the CM7 nigthly thread has a few suggestions on how to free space. Search not enough space on the nightlies thread.
Edit: I see you posted about the /data/data partition already.
Click to expand...
Click to collapse
Sent from my VS910 4G using XDA App
iowabeakster said:
Oh I know! It seems to catch everyone off guard because it works fine for X number of weeks or months and then... FC and freeze hell!
A lot of the folks found it happened shortly after upgrading from 7.0 to 7.1. But just in the last couple of days I have run across a couple of people that were still using 7.0 and now seem to have the issue.
The guy at CM who does most everything for the Dinc seems to think it was related to a full /data/data partition. I reinstalled fresh and did the ext4 "no data limit" mod, after first having the issue, and it made no difference at all. So, I gave up on CM the same day.
Click to expand...
Click to collapse
Don't let this Guy talk you out of cm7. I've been running the same kang for almost a month. And I ran the stable from October 9th til December 19th. It was always my fallback. I've never had issues, and as big as the nightlies/stable threads are. Why would you let one sway you?
-My life is a shooting range, people never change-
Correct, don't let one guy do that.
Certainly don't allow your own haywire experience affect your judgment.
And certainly don't allow these dozens of folks who posted on the CM incredible forum to have any influence on your decision.
http://forum.cyanogenmod.com/topic/32784-consistent-freezingfc-after-update-to-71/
Only listen to one guy who is running some OTHER build, that everything is perfect.
Your sarcasm is too advanced, my friend... ;] lol
iowabeakster said:
Correct, don't let one guy do that.
Certainly don't allow your own haywire experience affect your judgment.
And certainly don't allow these dozens of folks who posted on the CM incredible forum to have any influence on your decision.
http://forum.cyanogenmod.com/topic/32784-consistent-freezingfc-after-update-to-71/
Only listen to one guy who is running some OTHER build, that everything is perfect.
Click to expand...
Click to collapse
Sent from my ADR6300 using XDA App
Use Pons 7.2 kang. I've been since he started and all is well. I was running the nightlies before that and have never had any issues.
Ahhhhhhh
Sent from my HTC Incredible S
After the rather...disappointing way I departed and the resulting issues, I'm setting some things straight here and now.
1. No ETAs. Period. I don't want to see when will I fix or add anything.
2. No complaining. There's a line between reporting an issue and complaining. This line is crossed when it's reported more then once.
3. Requesting additions is fine, within reason. Keep it within reason, I'm not a real dev.
4. Using this ROM...this is where a lot of issues have come up, generally speaking, you can use this ROM as a base if you choose, however ASK ME FIRST. That's it! Everything could have been avoided if people had simply asked me before using my ROM and slapping their names on it then putting it out there. Please include some credit to waydownsouth, gh123man, randomblame and myself. For 4.3 Jellytime, randomblame in particular.
5. Hosting/mirroring. Please don't host or mirror this elsewhere, I will supply hosts for this ROM, I don't need more, and I prefer to keep track of how many users of a given build I have. Hosting elsewhere interferes with this. The only exception I can see is for our Russian/Ukrainian user community, my hosts may be slow there, or in other parts of the world. If you wish to host for another country, please let me know.
6. READ. For the love of all that is holy and great, READ the OPs, read at least the page before where your post will be. I will not answer questions already answered. If I respond, it may not be the nicest way I could do so. Please, save me, yourself, and everyone else the time and /facepalming and at least attempt to find the answer on your own. This is not limited to only this ROM, but anything you may wish to post about in this thread. Questions about CWM or TWRP don't belong here, but if they are valid questions that have something to do with this ROM, go ahead, after reading up on it.
7. Remaining on topic....well this one is loose. I prefer it to stay related only to this ROM, however I know things stray, and generally I'm OK with this, just try to keep it at least related to android. Or at least something related to something to do with on this planet.
Features:
Halo
PIE
Listview Animations (settings>display)
System Settings (CM)
Screenies:
Builds
Jellybean 4.1
Build 1 | Mirror
Kuroikaze-Sosei RC1
Kuroikaze-Sosei II B3 Final
Jellybean 4.3
Jellytime 4.3 - AFH | Jellytime 4.3 - DH
Gapps 4.1
http://goo.im/gapps/gapps-jb-20121011-signed.zip
Gapps 4.3
gapps-jb-20130813-signed.zip
Change log 4.1
Build 1: Updated to 4.1.2 sources. Generally stock CM10. Everything works. I think.
RC1: Based on Black Bean AOSP sources now.
Sosei II B3 Final:
Seeder
AC!D audio
XLoud
Supercharged
Die Hard launcher
init.d memory tweaks
time killer killer mod
maximum overdrive mod
service preserver
transition animations
Final release.
Change log 4.3
Ported from Randomblame's Jellytime Build 7
Build 1: Unreleased, initial trials to get it running. Bootloops.
Build 2: Unreleased, boots, but runs badly, storage is broken, audio stutters
Build 3: Almost everything works now, fixed storage via init/ramdisk entries
FULL WIPE NO MATTER WHAT
Broken in 4.1
RC1 -
Auto Brightness
Hardware Rotation Lock Switch (use software settings, it's more flexible anyways)
GPS
Fixed -
HDMI audio should now work (again)
Switchable UI (tab or phab UIs now)
Bugs-
In tab ui the clock is messing it's rear texture on the homescreen, ie its not black there, its wallpaper instead. Doesn't interfere with anything, just a glitch.
Huge thanks to justjackyl for testing this out for me and reporting back on issues.
FULL WIPE NO MATTER WHAT
Broken in 4.3
Mic
?
Untested:
GPS
HDMI
Bluetooth
Dock
Bugs:
WiFi will not reconnect if it turns off, a reboot is needed. Turning off the always scanning option seems to help this.
Forcing GPU acceleration can help even out the framerate in some cases.
4.1 Instructions:
Root and unlock your device, if you haven't, visit the All things Iconia A100 link in my sig, and read up. Then read again. Then proceed with rooting, unlocking, and installing a custom recovery.
I'm not going to note each recovery's method of installation, hopefully by now you guys know what to do in your recovery of choice.
Download the ROM to external SD
Download a current GApps package to your external SD card. Get one for JB, you can try a 4.2 package, but is as yet unsupported.
Reboot into recovery using whatever method you like:
-Power off then power on holding volume -
-Power menu>reboot>recovery if your ROM supports this
-App from the Play store reboot recovery
Full nandroid backup
FULL WIPE
-Factory reset
-Wipe System
-Wipe Dalvik
-Wipe Cache
Flash ROM (install from zip)
Flash appropriate GApps zip
Reboot system
Let system boot, allow up to 10 minutes for the GUI to come up from the boot animation
After the welcome setup wizard appears, let the tab sit for 10 minutes. Longer is fine.
Reboot tablet
Let sit 5 more minutes
Complete the setup wizard
Restore apps and whatever. Do not restore system apps and/or data
Restore user app data if you wish, but it may cause issues. If problems come up, factory reset and try again without restoring data.
Feel free to flash any kernel you want, but don't post about problems here until you use the kernel it came with first.
4.3 Instructions:
Root and unlock your device, if you haven't, visit the All things Iconia A100 link in my sig, and read up. Then read again. Then proceed with rooting, unlocking, and installing a custom recovery.
I'm not going to note each recovery's method of installation, hopefully by now you guys know what to do in your recovery of choice.
Download the ROM to external SD
Download a current GApps package to your external SD card. 4.3 ONLY! Don't report anything if you use anything but the gapps I linked from my site.
Reboot into recovery using whatever method you like:
-Power off then power on holding volume -
-Power menu>reboot>recovery if your ROM supports this
-App from the Play store reboot recovery
Full nandroid backup
FULL WIPE Don't report ANYTHING if you did not flash 100% clean!
-Factory reset
-Wipe System
-Wipe Dalvik
-Wipe Cache
Flash ROM (install from zip)
Flash appropriate GApps zip
Reboot system
Let system boot, allow up to 10 minutes for the GUI to come up from the boot animation. It may blank out for awhile on the first boot, just leave it be.
After the welcome setup wizard appears, let the tab sit for 10 minutes. Longer is fine.
Reboot tablet
Let sit 5 more minutes
Complete the setup wizard
I strongly recommend you download and install apps FRESH from the Play Store, and do NOT restore apps if possible. If you want, then go ahead...
Restore apps and whatever. Do not restore system apps and/or data
Restore user app data if you wish, but it may cause issues. If problems come up, factory reset and try again without restoring data.
Do not report any issues if you:
Dirty flashed.
Restored anything with any app.
Don't use the supplied kernel.
Modified the ROM in any way prior to the issue coming up.
Did not read the entire post and noted what bugs are already known to exist.
Did not use the 4.3 GApps on my site which I linked right below the ROM download.
Can not report a bug issue without quoting Hawkeye because you skipped all of this.
Thanks:
waydownsouth
randomblame
gh123man
godmachine / linux society
justjackyl
das_webos_transformer / xbooow
Cyanogenmod
AOKP
Team Baked
The Team behind the AC!D audio engine
Plus more, I'm sure.
HOLY SANTA CLAUSE ****!!!!!
CM9 Nightlies, Custom ROM, Rooting/Flashing Kit and "how to" tutorials
If there is anyone in the A100 community the deserves a donation it's this guy!
cdkg said:
HOLY SANTA CLAUSE ****!!!!!
CM9 Nightlies, Custom ROM, Rooting/Flashing Kit and "how to" tutorials
If there is anyone in the A100 community the deserves a donation it's this guy!
Click to expand...
Click to collapse
Roflmao so says my biggest donater!
Sent from my SGH-T989 using Tapatalk 2
You are the freaking man!
Sent from my A100 using xda app-developers app
Go for it.
You sir, are why I miss my Iconia A100 . Hopefully can get a new one soon, miss the A100 community
Sent from my SCH-I500 using Tapatalk 2
A big thank you !!!!!!!!!!!!!!!!!!!!!
So I got myself an A100 from ebay for 140 bucks just to toy with it and find its relevant thread on XDA to flash me some cm9 and what do I see. Working jb port completed already.. Imagine my shock !!!!! Hail *pio_masaki* .... you are the Man dude !!! :angel: Any amount of compliments I make is just insufficient to praise the amount of hard work and time you put behind this. :good::good::good::good: Just flashed v5-2 already and its "butter" smooth operation from then.. Wait till I show this to my friends...
rockthegod said:
So I got myself an A100 from ebay for 140 bucks just to toy with it and find its relevant thread on XDA to flash me some cm9 and what do I see. Working jb port completed already.. Imagine my shock !!!!! Hail *pio_masaki* .... you are the Man dude !!! :angel: Any amount of compliments I make is just insufficient to praise the amount of hard work and time you put behind this. :good::good::good::good: Just flashed v5-2 already and its "butter" smooth operation from then.. Wait till I show this to my friends...
Click to expand...
Click to collapse
Thanks, and welcome to our little corner of XDA! Hope your new tablet is as good as mine has been to me
But really guys, randomblame did the hard work on this. I just got it running on the A100.
Pio, I know the feeling on the time spent on these things and friction with the wife. Use lube, Red Wine is what I suggest, good for the heart.
Jk buddy, thanks for all your work and time. Family first. We understand.
wild1z said:
Pio, I know the feeling on the time spent on these things and friction with the wife. Use lube, Red Wine is what I suggest, good for the heart.
Jk buddy, thanks for all your work and time. Family first. We understand.
Click to expand...
Click to collapse
Thanks for the understanding.
Also....new version with WiFi and some sound is up. Root seems to work to a point but I'll say its broken for now.
tapatalked from my A100 - Jellytime V7.7
unbelievable, I am bewildered by this topic! fantastic!
Pio_masaki,I have been a silent observer of your threads for quite a while, and I have to say that I have never seen such a nice person as you. Maybe there're other developer in XDA that has a better skill than you (just maybe, haha, please don't be offended =p), but regarding personality and character, I think no one can match you. You really deserve the best person award. Thanks for all the work that you have done to the community =)
xitrumch said:
Pio_masaki,I have been a silent observer of your threads for quite a while, and I have to say that I have never seen such a nice person as you. Maybe there're other developer in XDA that has a better skill than you (just maybe, haha, please don't be offended =p), but regarding personality and character, I think no one can match you. You really deserve the best person award. Thanks for all the work that you have done to the community =)
Click to expand...
Click to collapse
Thank you for the kind words, and no I'm not offended, there are certainly much better developers for sure, as I don't really consider myself a developer anyways. Most of this work has been done by randomblame and waydownsouth I just move it over for us on the A100, which isn't always easy I'll admit.
Version 7.8 is now available
Change log:
Root is now working as it should.
Open Super SU
Let it "install" binary (its already there)
Enjoy
External SD is now RW:
Fixed a permission issue in platform.xml to allow full read/write to external_sd.
Brightness control now works:
Auto brightness doesn't seem to work, manual brightness works. This was actually fixed in a previous release, and broke again, and is now working again.
Sound:
Sound works in some apps, but system sound is still broken, ie notifications, music, but some apps/games work, like angry birds now has audio.
Bluetooth:
Bluetooth has been proven fixed by a pairing, testing done by ntan97.
Still Broken:
Gallery/camera
Internal SD doesn't mount
Power LED is erratic, sometimes always on, sometimes always off
Home to wake: works when power led is ON, doesn't work while it is OFF
Video playback is still broken. Tested on stock player, dice player, mp4 and avi.
I'll be redoing the posts to be a little less confusing by moving things to change logs like this.
Wow man. I'm surprised on how much progress you're making on this. It's quite a feat. You can say all you want about how you're just compiling what others have made to the A100, but it takes a good person to continue a project for such a small community like this (even after you said you were going to slow down? I haven't seen you slow down at all) and it's still not just that simple.
You're probably one of the most helpful people here since crossix. Thanks for you're work :thumbup:
Hopefully when I receive a new PC in a couple weeks I could start making the first complete A100 theme for this ROM. To my knowledge there really hasn't been a whole lot of action in the themeing department here.
Sent from my A100 using Tapatalk 2
notsointeresting said:
Wow man. I'm surprised on how much progress you're making on this. It's quite a feat. You can say all you want about how you're just compiling what others have made to the A100, but it takes a good person to continue a project for such a small community like this (even after you said you were going to slow down? I haven't seen you slow down at all) and it's still not just that simple.
You're probably one of the most helpful people here since crossix. Thanks for you're work :thumbup:
Hopefully when I receive a new PC in a couple weeks I could start making the first complete A100 theme for this ROM. To my knowledge there really hasn't been a whole lot of action in the themeing department here.
Sent from my A100 using Tapatalk 2
Click to expand...
Click to collapse
Yeah....I keep saying ill slow down.....then I get a new idea or theory and go back until I get it right lol
Theme wise stetsonaw has a complete theme that works for us, but of course more is always better, I'm partial to black and red myself.
And PC...yeah don't get me started on that. My fastest machine takes 3 hours to build. That's like 2 hours of prepping 3 hours to build just to test. Unless its something I can do after compiling. That's the version number, first is build second is changes within that build after its built. So current is build 7 change 8, so figure 3 hours per build, plus whatever time of work before the build, plus whatever hour so per change after... plus the builds I didn't even number lol.
All said and done I have at least 21 hours invested in builds. Probably another 15 in smaller revisions, plus the 9 hours getting the initial port worked out. Over...maybe 2 or 3 weeks. Plus the nightly cm9 builds. And a few hours for the scripts, few more for aoikaze, and more on kuroikaze which I'll likely never finish and release. Oh and the guides lol.
It adds up quick. This is just since May...I think closer to June when I started all of this.
Edit: Just realized I have over 99 hours in the nightly cm9 builds, not counting setting up for it and uploading time lol
tapatalked from my A100 - Jellytime V7.9
I just flashed and have noticed one thing (I apologize if already stated just haven't seen)
But it looks like just a density issue. Fonts are just small at times. The stock launcher seems a little weird and when in landscape the notification bar is far on the left.
I tried my best to take a photo.
And just a question. Are their specific 4.1 gapps or are the ICS ones the same?
You can follow me on Twitter - @NotSo1nter3stin
notsointeresting said:
I just flashed and have noticed one thing (I apologize if already stated just haven't seen)
But it looks like just a density issue. Fonts are just small at times. The stock launcher seems a little weird and when in landscape the notification bar is far on the left.
I tried my best to take a photo.
And just a question. Are their specific 4.1 gapps or are the ICS ones the same?
You can follow me on Twitter - @NotSo1nter3stin
Click to expand...
Click to collapse
Yeah not a bug, that's the new 7" UI jellybean uses. Not sure why they killed the combined bar and chose a phone UI though. That's how the N7 will look too.
Oh edit there is a jb gapps but they're kinda broken, so flash them, ten icss gapps over it and itll work, that's how I do it. I'll add them into the OP sometime today, niece and nephew are staying with us for a few days so I'll be busy being the coolest uncle ever with all my modded consoles, devices and toys lol
tapatalked from my A100 - Jellytime V7.9
pio_masaki said:
Yeah....I keep saying ill slow down.....then I get a new idea or theory and go back until I get it right lol
Theme wise stetsonaw has a complete theme that works for us, but of course more is always better, I'm partial to black and red myself.
And PC...yeah don't get me started on that. My fastest machine takes 3 hours to build. That's like 2 hours of prepping 3 hours to build just to test. Unless its something I can do after compiling. That's the version number, first is build second is changes within that build after its built. So current is build 7 change 8, so figure 3 hours per build, plus whatever time of work before the build, plus whatever hour so per change after... plus the builds I didn't even number lol.
All said and done I have at least 21 hours invested in builds. Probably another 15 in smaller revisions, plus the 9 hours getting the initial port worked out. Over...maybe 2 or 3 weeks. Plus the nightly cm9 builds. And a few hours for the scripts, few more for aoikaze, and more on kuroikaze which I'll likely never finish and release. Oh and the guides lol.
It adds up quick. This is just since May...I think closer to June when I started all of this.
Edit: Just realized I have over 99 hours in the nightly cm9 builds, not counting setting up for it and uploading time lol
tapatalked from my A100 - Jellytime V7.9
Click to expand...
Click to collapse
Bit off topic... but woah, thanks man. Just donated 5€
does anyone know, or have a reason, or encounted in a problem with CM 10.1 cuz i recently installed CM 10.1 stable on my ATT S3 and it keeps restarting itself after 20/30 minutes tops, maybe longer but once in a while it randomly restarts itself
installed everything perfectly, no reason to be acting crazy since its from CYANOGENMOD TEAM but ROMS are not perfect or as good as STOCK ROMS (that come pre-installed on your device)
any issues, bugs, any kind of thing you have noticed with cm 10.1 yu can post it here
new upcoming features, fixes, what should be there or shouldnt be there, whats missing everything
HELPING EACH OTHER SOLVE SIMPLE/SERIOUS with CM 10.1 and above ISSUES
am currently running Synergy ROM 4.1.2 Stock rom with ZIGGY KERNEL (clocked at 1.3 Ghz) and its pretty sweet, stable, good battery, perfomance is top notch for a stock based rom that come with all samsung boatload
SO DUMP ALL THE PROBLEMS/SOLUTIONS IN THIS NEW THREAD FOR CM 10.1 AND ABOVE - ATT S3 I747
ANYTHING YU THINK IS COOL/AWSOME ABUT CM 10.1 ON YOUR AWSOME S3 GET IT HERE
Or just post them in this thread which already gets developer support.
http://forum.xda-developers.com/showthread.php?t=1778270
Not all phones are created equal. You should try the newer nightlies since they're just as stable. I haven't had any issues with Cyanogenmod. The reboot bug has been squashed a couple of months ago for me.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Domoo said:
Or just post them in this thread which already gets developer support.
http://forum.xda-developers.com/showthread.php?t=1778270
Not all phones are created equal. You should try the newer nightlies since they're just as stable. I haven't had any issues with Cyanogenmod. The reboot bug has been squashed a couple of months ago for me.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Click to expand...
Click to collapse
thanks for that, but this thread is based on everything to do with cyanogenmod 10.1 and above, clearly i am not a fan of nightlies as to do with updating my phone every second (thats a hustle for me cuz i gotta backup everything/reinstall everything again) and not to mention i have better things to do than just updating to a new bulds everyday or trying new roms
ihave too much variable things on my phone to delete for reasons like nightlies
THE REBOOT BUG STILL exists quite suprisingly for me as you dont have problems with nightlies or the reboot bug too
the thread yu mentioned is helpful but new ideas, new thoughts, easy to find a solution for a problem/question and navigate easly without having to dig it up tens of pages, a new thread with new people/same but fast replies, nice to workaround with.
am not trying to break any XDA rules/regulations or whatsoever by posting/asking a question or starting a thread thats already there(content and information that i need) but a new thread thats clean, new ideas about the rom, new problems/solutions is what this thread is all about
PHONES COULD BE EQAUL BUT ROMS ARE NOT SAME/DONT WORK SAME ON XXXXX PHONE
winosxbuntu said:
thanks for that, but this thread is based on everything to do with cyanogenmod 10.1 and above, clearly i am not a fan of nightlies as to do with updating my phone every second (thats a hustle for me cuz i gotta backup everything/reinstall everything again) and not to mention i have better things to do than just updating to a new bulds everyday or trying new roms
ihave too much variable things on my phone to delete for reasons like nightlies
THE REBOOT BUG STILL exists quite suprisingly for me as you dont have problems with nightlies or the reboot bug too
the thread yu mentioned is helpful but new ideas, new thoughts, easy to find a solution for a problem/question and navigate easly without having to dig it up tens of pages, a new thread with new people/same but fast replies, nice to workaround with.
am not trying to break any XDA rules/regulations or whatsoever by posting/asking a question or starting a thread thats already there(content and information that i need) but a new thread thats clean, new ideas about the rom, new problems/solutions is what this thread is all about
PHONES COULD BE EQAUL BUT ROMS ARE NOT SAME/DONT WORK SAME ON XXXXX PHONE
Click to expand...
Click to collapse
First and foremost, no OS or software, including android, is perfect. Secondly starting a new thread does not mean it will not get "cluttered" either. The ROM thread for CM is not as bad as you make it out to be. The idea is that the newest material covers the most recent nightlies. It is not that difficult to go to the end and work backwards. In regards to you random reboots, look on JIRA as it exists for this very reason. Take a logcat and report on JIRA if not already covered. JIRA gives you all the bugs reported and their current status towards a fix. This is a wasted thread for this very reason.
As far as ROMs being different...that is the point. Each developer(s) put their own spin on it. That is what makes these development threads so great. You can look for a ROM that you like best. Some ROMs are more universal (but you still need your device specific version), such as CM, while others are device specific.
And phones are not created equal. They may look the same, have the same hardware specs, and all else seemingly equal, but slight manufacturing imperfections make them different. Two people can have the exact same phone from the same carrier, manufactured on the same day, but due to some ever so slight differences from imperfections, ROMs will work differently on each. For instance, in your case CM reboots randomly. For others, such as myself, this is no longer an issue. However, it is possible that another ROM will work great on your phone but not on mine.
While you say CM is not perfect like the stock rom, the stock rom is not perfect either. I have AT&T and the stock rom has several issues. The lockscreen securities can be bypassed, the alarm likes to not work at random times (software bug), and every now and then I get a battery plummet after a phone call when the phone switches between 4G and 4G LTE. Others may or may not have these issues but they seem to be rather common (the security bypass affects all S3 phones that were on 4.1.1 that I am aware of). For this reason I stick to custom roms because I do not have these problems which I personally view as severe for me (Aside from protecting my data and enjoying battery life, I rely on my phone as an alarm clock). Now that 4.2.2 has come as far as it has, it is stable enough that I can use it as a daily driver. I knowingly accept any bugs that are there because typically the ones that exist do not have a large affect on me, if at all, unlike the stock rom.