Would post in the pac-man thread, but have less than 10 posts.
Recently flashed the latest version of pac-man from pio (6/11). Did a clean flash. When i went to install titanium backup, I got an error that the device isn't rooted. Looks like there is no superuser app installed.
Is this an issue where pio accidentally failed to include superuser? Is it something i can download and sideload?
Any help appreciated.
Thanks!
duskdrums said:
Would post in the pac-man thread, but have less than 10 posts.
Recently flashed the latest version of pac-man from pio (6/11). Did a clean flash. When i went to install titanium backup, I got an error that the device isn't rooted. Looks like there is no superuser app installed.
Is this an issue where pio accidentally failed to include superuser? Is it something i can download and sideload?
Any help appreciated.
Thanks!
Click to expand...
Click to collapse
Flash below file from recovery.
www.mediafire.com/?oc6j43h8c5vmtvw
DNA | ⓣⓐⓟⓐⓣⓐⓛⓚ | TF300T
duskdrums said:
Would post in the pac-man thread, but have less than 10 posts.
Recently flashed the latest version of pac-man from pio (6/11). Did a clean flash. When i went to install titanium backup, I got an error that the device isn't rooted. Looks like there is no superuser app installed.
Is this an issue where pio accidentally failed to include superuser? Is it something i can download and sideload?
Any help appreciated.
Thanks!
Click to expand...
Click to collapse
Its integrated into the ROM now, I couldn't forget it if I wanted to. This happens on occasion, you can either flash it yourself as suggested or flash the ROM again, either should get it going.
Tapatalked from my HTC DNA - Carbon
thanks!
pio_masaki said:
Its integrated into the ROM now, I couldn't forget it if I wanted to. This happens on occasion, you can either flash it yourself as suggested or flash the ROM again, either should get it going.
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
Thanks! Worked great. i flashed it myself, but I see from the main thread that I should delete the app before flashing the next update.
Didn't mean to impugn your awesome dev skills by saying "forget." was actually meant in jest, but i see that didn't come across in the OP.
Thanks again for a fantastic rom!!!
duskdrums said:
Thanks! Worked great. i flashed it myself, but I see from the main thread that I should delete the app before flashing the next update.
Didn't mean to impugn your awesome dev skills by saying "forget." was actually meant in jest, but i see that didn't come across in the OP.
Thanks again for a fantastic rom!!!
Click to expand...
Click to collapse
I didn't take offense to it, just stating its built in now, where it used to be an app by itself, which could be forgotten lol
Tapatalked from my HTC DNA - Carbon
pio_masaki said:
Its integrated into the ROM now, I couldn't forget it if I wanted to. This happens on occasion, you can either flash it yourself as suggested or flash the ROM again, either should get it going.
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
Pio- I'd post into the Pac Man thread but I'm still not at 10 posts yet. I downloaded and flashed your ROM maybe 20 hours ago, and I don't have SU either. Was it updated between then and now? My time zones are off...
Also, I'm getting some app FCs, specifically Google Play Music>My Library. I did a clean install and I'm using crpalmer's kernel. I've seen people talking about this specific bug as far back as 5/8 in the CM thread, but no one's posted about it recently. Do you know if this was fixed/is it CM/is it crpalmer's kernel? Music is probably one of my most essential apps...
BTW great work this ROM is awesome
Bartikus said:
Pio- I'd post into the Pac Man thread but I'm still not at 10 posts yet. I downloaded and flashed your ROM maybe 20 hours ago, and I don't have SU either. Was it updated between then and now? My time zones are off...
Also, I'm getting some app FCs, specifically Google Play Music>My Library. I did a clean install and I'm using crpalmer's kernel. I've seen people talking about this specific bug as far back as 5/8 in the CM thread, but no one's posted about it recently. Do you know if this was fixed/is it CM/is it crpalmer's kernel? Music is probably one of my most essential apps...
BTW great work this ROM is awesome
Click to expand...
Click to collapse
The issue you mention aren't app FC, they simply close, vanish, no FC message, you have a different issue that requires more information before I'll hazard a guess. If you read anything in the PAC thread you'll see what I want in a post saying there's an issue.
Tapatalked from my HTC DNA - Carbon
pio_masaki said:
The issue you mention aren't app FC, they simply close, vanish, no FC message, you have a different issue that requires more information before I'll hazard a guess. If you read anything in the PAC thread you'll see what I want in a post saying there's an issue.
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
Well, this is what I came up with as far as bug reporting in your posts:
Q. I want to report an issue, can I just post it in your thread without reading or doing any basic troubleshooting, googling, reading or wiping?
A. Well you CAN, you may be ignored or flamed for it. Please read above, and please read the Bugs and Change Log lists before reporting anything. Please flash a clean download, flash a clean wipe, and don't restore stuff from TiBu, thats basic troubleshooting, check if the issue persists, if it does, then feel free to post about it.
I always read the bugs and change logs, that's one of my criteria for picking a ROM. I downloaded your PAC-Man ROM last night, put it on my SD card, along with inverted and regular Gapps. I wiped data, cache, and dalvik. Then I flashed your ROM, then the inverted Gapps and rebooted. Decided I didn't like the inverted, booted back into recovery, wiped data, cache, dalvik again. Flashed regular, most recent Gapps. Rebooted again. Thought about it, and then decided to try crpalmer's kernel. AGAIN, wiped data, cache, and dalvik before flashing. Everything seemed fine, I began installing apps from the play store (I don't use anything to back up apps, no TiBu or anything) and went to bed. It wasn't until this morning when I was setting up my BT in the car and opened Play Music for the first time. I can play music, I can search, I can go to radio, etc. It only crashes/closes/disappears if I go to My Library. I don't have SU either which I noticed at work today, which is what lead me to post here in the first place.
That's as descriptive as I can be. I hope it helps
Bartikus said:
Well, this is what I came up with as far as bug reporting in your posts:
Q. I want to report an issue, can I just post it in your thread without reading or doing any basic troubleshooting, googling, reading or wiping?
A. Well you CAN, you may be ignored or flamed for it. Please read above, and please read the Bugs and Change Log lists before reporting anything. Please flash a clean download, flash a clean wipe, and don't restore stuff from TiBu, thats basic troubleshooting, check if the issue persists, if it does, then feel free to post about it.
I always read the bugs and change logs, that's one of my criteria for picking a ROM. I downloaded your PAC-Man ROM last night, put it on my SD card, along with inverted and regular Gapps. I wiped data, cache, and dalvik. Then I flashed your ROM, then the inverted Gapps and rebooted. Decided I didn't like the inverted, booted back into recovery, wiped data, cache, dalvik again. Flashed regular, most recent Gapps. Rebooted again. Thought about it, and then decided to try crpalmer's kernel. AGAIN, wiped data, cache, and dalvik before flashing. Everything seemed fine, I began installing apps from the play store (I don't use anything to back up apps, no TiBu or anything) and went to bed. It wasn't until this morning when I was setting up my BT in the car and opened Play Music for the first time. I can play music, I can search, I can go to radio, etc. It only crashes/closes/disappears if I go to My Library. I don't have SU either which I noticed at work today, which is what lead me to post here in the first place.
That's as descriptive as I can be. I hope it helps
Click to expand...
Click to collapse
Very nice lol
The most recent PAC has a broken super user, flashing a super user zip will work or you can use the previous build where the integrated super user works. There was a link posted in the main PAC thread as well as here in this thread I think.
Google music library does seem to be problematic, though it may be halo related, Google music has had issues on alot of the AOSP type ROMs from streaming to vanishing to now having library issues, it seems to occur more on local files vs cloud, though.
Does this occur on the stock kernel also? I know you mentioned flashing crpalmers kernel, just wondering.
Tapatalked from my HTC DNA - Carbon
pio_masaki said:
Google music library does seem to be problematic, though it may be halo related, Google music has had issues on alot of the AOSP type ROMs from streaming to vanishing to now having library issues, it seems to occur more on local files vs cloud, though.
Does this occur on the stock kernel also? I know you mentioned flashing crpalmers kernel, just wondering.
Click to expand...
Click to collapse
Well I know very little about Halo, but I can say that I was able to stream just fine over 4g if I played the music without going through the My Library tab (search, Listen Now, etc.). I didn't have any local files at all since it was just after a wipe.
I did another clean install of your ROM last night, flashed the Gapps from goo.im, and DID NOT flash crpalmer's kernel. Same issue
Bartikus said:
Well I know very little about Halo, but I can say that I was able to stream just fine over 4g if I played the music without going through the My Library tab (search, Listen Now, etc.). I didn't have any local files at all since it was just after a wipe.
I did another clean install of your ROM last night, flashed the Gapps from goo.im, and DID NOT flash crpalmer's kernel. Same issue
Click to expand...
Click to collapse
Supposedly fixed if you update it.
Tapatalked from my HTC DNA - Carbon
pio_masaki said:
Supposedly fixed if you update it.
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
I assume you mean Play Music. All my apps are up to date, though. I'm on my lunch break now I'll try wiping the app's data and cache, see if that works, and if not I'll uninstall it, reinstall and see if there's any difference.
UPDATE: Neither of the above attempts solved it. Also Play Music > Radio causes the same kind of close. Now I can't remember if it did it before or not. I also noticed that there was a "blacklist Halo notifications" option, I tried that as well to no effect.
OK so for the developers, the apps just closing like that, was a few commits to cm10.1 source, particularly bionic and dalvik, some optimisations regarding krait CPU stuff got applied to all phone types which caused the issue,
Superuser pac-man source fixed that issue a day or 2 ago in vendor-pac and settings
onejay09 said:
OK so for the developers, the apps just closing like that, was a few commits to cm10.1 source, particularly bionic and dalvik, some optimisations regarding krait CPU stuff got applied to all phone types which caused the issue,
Superuser pac-man source fixed that issue a day or 2 ago in vendor-pac and settings
Click to expand...
Click to collapse
Yeah this is all known, for whatever reason the changes made weren't merged like I thought they would be so the issue persisted and I just haven't had time build another one, the workaround for now is sufficient.
Tapatalked from my HTC DNA - Carbon
Related
[Q] Browser doesn't work on CELB Froyo 4.3 =(? HELP!
1. Check 3G signal, basically is the internet working?
2. Try re-flashing CELB and make sure to flash the latest gapps too
It would be more helpful if you gave a more in depth view of your browser problem.
it would help you more if you posted this issue in CELB's thread. You will get better answers faster by people who use the rom and that may have came across the isssue
When i try to reply it says i can't and should start using the Q&A Thread? smh
BBoY177 said:
When i try to reply it says i can't and should start using the Q&A Thread? smh
Click to expand...
Click to collapse
That's due to a recent change in XDA's site policy - new users can not post in the development sub-forums until they have at least 10 posts in other forums. So, you were right to post your question here, as you had no other choice. DirtyBubble apparently wasn't aware of this either, or he wouldn't have said that.
I tried a fresh install of 4.3 last night (w/ gapps 12/28), no bootloops, but no market access or Google account setups either. I'm going to look at a few different installs in a couple minutes - check back in this thread later.
bftb0
I tried the following 3 trials:
Before starting, I did a Nandroid backup (from within ROM Manager/Clockworkmod) of my existing ROM - CELB 4.1. (I am not sure of whether this 4.1 ROM had gapps 12/28 in it or not - I believe it does, but iirc they were installed on a CELB 3.9 ROM, and then just overflashed to 4.1)
1) Wipe Cache, Wipe Data/FR, Flash CELB4.3, Flash gapps 12/28
Result: account setup does not occur; market app crashes or closes immediately. Tried doing a FR on this; next boot the kernel actually crashed. Didn't bother to check the browser**
2) Wipe Cache, Wipe Data/FR, Flash CELB4.3, Flash gapps 10/18
Result: Provided account creds; phone sync'ed just fine and restored settings; Market works; Web Browser worked.
3) Wipe Cache, Wipe Data/FR, Restore CELB 4.1 from Nandroid backup; Flash CELB4.3; Wiped CACHE ONLY.
Result: Everything works, including stock browser.
** I didn't bother to check the browser in this case because I have little interest in using a ROM without a Gmail account; it did occur to me later, though, that the default setting of the browser has been to use location-services, and that the stock browser has exhibited crashes on startup on other ROMs that did not have a Google account configured. You can turn this off in the browser - but only if it doesn't crash, because you need to get to the browser settnigs menu to deal with this, so that is impossible in this case.
I don't know if that is your issue or not, but you could try turning off location services in the Settings menu and see if that makes any differences. (I don't know if that will work, but it is easy to try). Anyway, that's two solutions: either overflash 4.3 on top of a prior CELB ROM, or do a clean install of 4.3 using the 10/18 gapps. (If you do the former, you can only wipe cache at the end if you are using ClockworkMod - or manually via ADB if you are booted into Amon_RA).
bftb0
The AOKP build works great except for the constant disappearing keyboard that is about to make me kick puppies. I saw the note to install the wingray google apps to avoid the disappearing keyboard that is synonymous with the recommend gapps to use, but my dumb ass forgot and installed the recommenced apps and I surely do have the constant disappearing keyboard issue. I have flashed the "gapps-jb-20130129-P75xx" zip but still have the issue. Do I have to wipe everything and start over? Does flashing the new gapps zip not overwrite the "gapps-4.2.2-jb-3.4.2013-signed" I originally installed? It seems not to, but wanted confirmation before wiping everything again.
You should wipe everything and start over. IMHO.
Full wipe and used the "gapps-jb-20130129-P75xx". Disappearing keyboard will no longer boil my blood.
For reference, never use the "gapps-4.2.2-jb-3.4.2013-signed".
Glad I stumbled onto this thread. Exactly the problem, keyboard, (well one of them anyway) I am having.
Well for me I can't find anything to fix the disappearing keyboard issue. I tried using the suggestions above. No help. After finding more and more posts in the same subject on different boards it seemed only the Wingray gapps is the one that works properly. Just tried that one and it doesn't seem to fix the issue either. Tried several of the newer nightly ROMs too.
One suggestion was to download the Go keyboard. That didn't help either.
Dang how hard can this be? I have flashed and wiped cache so many times lately. lol
The problem why is exactly explained in nakedninja's 4.2.2 thread, you should read before you install anything
DefQoN_BE said:
The problem why is exactly explained in nakedninja's 4.2.2 thread, you should read before you install anything
Click to expand...
Click to collapse
Unfortunately that thread content has not helped in my case. I found that thread early on and have tried to follow the directions. So either I'm missing something or not doing something correctly it appears.
Someone in another forum suggested I try the free Jellibean keyboard.
I had this issue too with AOKP 4.2.2. I have not reflashed another new gapps yet, as I found re-installing a third-party keyboard which I liked from previous use solved the problem.
Andre
Well whatever I did I finally fixed it. I ended up simply formatting the internal SD card. Poof, everything gone. Had to restore from backup default ROM. Once the stock firmware was up and running I followed the procedures again. Wiped, cleared cache multiple times and when it was all done installing there is no more keyboard issue as of now.
I loaded the 4/08/2013 nightly ROM and Wingray gapps(which I've already tried multiple times). So all is well in Tablet land again.
I've recently installed AOKP(Jellybean 4.2.2) Task650 (http://forum.xda-developers.com/showthread.php?t=1808015) and the basic install seemed to go very well. I came from stock 4.0.4 (rooted) and for the record I'm using Recovery 6.0.3.0 and I did a full wipe including format system, data, cache, dalvik etc. I installed the new gapps after the ROM, and later restored apps using Titanium.
I have a few issues I can't quite sort out though, and I'm not sure if they are JB, Nova or AOKP related so I thought I'd start a new thread.
1) Lockscreen doesn't appear. At all. When I wake the tablet up, it just comes straight back on to the previously used screen. I've checked all the standard Security settings (unlock mode set to slide or pattern, lock on power button, etc) and also the fancier AOKP ones, but whatever I do the lockscreen just does not appear. I've re-cleared cache and dalvik.
2) Notifications are not showing in the Notifications area. I can see the AOKP 'Toggles' icons/tiles for wi-fi, bluetooth, GPS, etc; the clock; the battery level; the wi-fi SSID, etc - but no general Notifications at all (e.g. list of any updated apps, any download statuses, Poweramp mini controls, new emails/facebook messages, Samba active display, etc).
When these various notification are issued, I do see them appear briefly in the lower-right corner in a grey rectangular box which covers the clock/battery area of the status bar (so the notifications do appear to be triggering) but as soon as that brief message disappears, I can't see any of the notifications within the pop-up notifications area where they should be.
Does anyone familiar with JB, AOKP or this particular ROM have any suggestions, as I'm as a loss at the moment?
Andre
Ah, no-one with any ideas of where these issues might be coming from then?
I might have to try another full-wipe install, and if that fails just go back to stock 4.0.4 until (if ever) Samsung releases a JB update for the original 10.1 tab.
Andre
andrewilley said:
Ah, no-one with any ideas of where these issues might be coming from then?
I might have to try another full-wipe install, and if that fails just go back to stock 4.0.4 until (if ever) Samsung releases a JB update for the original 10.1 tab.
Andre
Click to expand...
Click to collapse
I'm not familiar with that rom, but there are a few things you can try.
1. Try posting in the development thread, it might be a known issue that has a quick fix.
2. If you really want to stick with that rom try the full wipe again. But since you already started with one I don't know if it will fix the problems.
3. If you want to stay with jb I would recommend Aopk build 6 by djmatt604. It runs smoothly and the dev is pretty active.
Hope this helps even a little.
kilometers4 said:
I'm not familiar with that rom, but there are a few things you can try.
1. Try posting in the development thread, it might be a known issue that has a quick fix.
2. If you really want to stick with that rom try the full wipe again. But since you already started with one I don't know if it will fix the problems.
3. If you want to stay with jb I would recommend Aopk build 6 by djmatt604. It runs smoothly and the dev is pretty active.
Click to expand...
Click to collapse
Many thanks for the reply. I have searched and asked in the dev's thread, but I get the very clear impression that if it works on his hardware and no one else has the same problem, his opinion is that it's 100% up to me to sort it out - which is entirely his prerogative, of course: his ROM, his thread, his rules.
Thanks for the recommendation of another AOPK option (I assume you mean [ROM][P7510][4.2.2][UNOFFICIAL] AOKP Build 6 :: MR1 :: Mar 29 Nightly). I think I might go down that route since, like you, I'm rather dubious that another full-wipe will be any different to the first one.
Andre
andrewilley said:
...
Thanks for the recommendation of another AOPK option (I assume you mean [ROM][P7510][4.2.2][UNOFFICIAL] AOKP Build 6 :: MR1 :: Mar 29 Nightly). I think I might go down that route since, like you, I'm rather dubious that another full-wipe will be any different to the first one.
Andre
Click to expand...
Click to collapse
Yup that's the one. I'd recommend doing a full wipe on the first install to avoid issues. Let me know if you have any other questions.
I went with [ROM][KERNEL][RECOVERY][JB4.2]Infamous AOKP 1.4 (14-Apr-13) in the end, from the same dev you suggested. I added Nova as my launcher and it all works like a charm (well, after I recovered myself from a stupid near-brick when I decided to format the user sdcard in order to clear out any remaining junk from old installs; it cleared out a lot more than I wanted!!!)
Andre
andrewilley said:
I went with [ROM][KERNEL][RECOVERY][JB4.2]Infamous AOKP 1.4 (14-Apr-13) in the end, from the same dev you suggested. I added Nova as my launcher and it all works like a charm (well, after I recovered myself from a stupid near-brick when I decided to format the user sdcard in order to clear out any remaining junk from old installs; it cleared out a lot more than I wanted!!!)
Andre
Click to expand...
Click to collapse
Yeah, I usually just wipe data / Factory reset when doing a full wipe and then go in manually and clean out folders that I don't need to clear space. SD maid is a good app for clearing unused space too.
kilometers4 said:
Yeah, I usually just wipe data / Factory reset when doing a full wipe and then go in manually and clean out folders that I don't need to clear space. SD maid is a good app for clearing unused space too.
Click to expand...
Click to collapse
Yeah, I'm normally the same but I thought I'd be nice and thorough for once and get rid of any remaining legacy ICS stuff which some JB updates shove into hidden folders when you upgrade. In hindsight, I shouldn't have bothered.
Still, at least when I finally did get the system recovered enough to install the new ROM, the free space was amazing!
Andre
I got the same problem...how to solve it bro....
srinuchry said:
I got the same problem...how to solve it bro....
Click to expand...
Click to collapse
I think the problem may have been with something that Titanium Backup restored from my previous setup, but I never found out what. I had to do a factory reset to clear it in the end (although not a full ROM reinstall).
As I'd already gone that far though, rather than risking re-installing apps again I actually chose another ROM anyway - Infamous (see above) - which I'm very happy with, and the devs there seem much happier to talk to you in general. Just my observation anyway, your experiences could well be quite different of course.
Andre
This is a Deodexed Version Of the newest JellyBean 4.2.2 Leak N5110XXCMG2
Features:
Rooted
insecure boot.img
BusyBox
Zipaligned
Deodexed
Init.d support
adb as root
Bash
Nano
Download: http://www.androidfilehost.com/?fid=23050663588004205
md5: 0386dd0afe5fd788ae2486b7820cfddd
Disclaimer: nothing has been edited this is a full stock rom that you would expect to get from samsung just rooted and deodexed for easy modability,themability
Thanks to:
SamMobile - for the basefirmware package
Dsixda - for the kitchen used to deodex
ChainFire - for superSU
FYI- i will be making me JellyBeans Rom with this base
Welcome back .
Is there much difference between this version and civato other than his has Aroma installer?
2swizzle said:
Welcome back .
Is there much difference between this version and civato other than his has Aroma installer?
Click to expand...
Click to collapse
this is pure stock deodexed nothing removed, and has adb as root. also doesnt have any mods
thank you for posting this here! :good:
Many thanks!
Thanks for this! Works great, feels more fluid... Except doesn't seem to fix the touchscreen deadzones that occur intermittently (but of course that's for Samsung to take care of)
How this update should be installed? Adb?
Edit. Sorry, never mind, this is for N5100 but I have N5100. Waiting for new version for my device.
I am interested in loading this rom on my wife's tablet. I have been flashing rom's on my Motorola Phones for years now and am very comfortable doing so, but a real Novice when it comes to Samsung.
I am on 4.1.2, insecure loader. I have tried both CWM and TWRP recoveries and can use either. I have also used Odin as well.
Question, do I need to wipe data first, and how do I load this rom onto a Samsung Device.
Sorry for the trouble, but I am a fast learner and will be on board soon (I hope)
BobC43 said:
I am interested in loading this rom on my wife's tablet. I have been flashing rom's on my Motorola Phones for years now and am very comfortable doing so, but a real Novice when it comes to Samsung.
I am on 4.1.2, insecure loader. I have tried both CWM and TWRP recoveries and can use either. I have also used Odin as well.
Question, do I need to wipe data first, and how do I load this rom onto a Samsung Device.
Sorry for the trouble, but I am a fast learner and will be on board soon (I hope)
Click to expand...
Click to collapse
Since this is an OS upgrade (4.1.2 to 4.2.2) a data wipe is highly suggested. Frankly, I would suggest wiping system, data, cache and dalvik just for good measure. If she wants to keep a lot of the apps' progress/settings she has, I would install Titanium Backup and back up all user apps first before doing anything. She may have everything synced with her Google account as I believe you can sync apps and their data through Google now, but I haven't tested it yet.
To install the ROM, you'd just need to put it somewhere locally on your tablet, I have a '000Flash' folder on the root of my internal SD storage for any ROMs/kernels/modems (on my phone), etc. Place it in there, then get yourself into recovery. Once in recovery, wipe everything I mentioned above, then go back to the install/flash option of whatever recovery you're using. Flash the .zip file you just downloaded and put locally on your tab. Wait a few minutes and boot her up!
Just make sure you have the right software for the right version tablet you have, N5110 vs N5100.
hayzooos said:
Since this is an OS upgrade (4.1.2 to 4.2.2) a data wipe is highly suggested. Frankly, I would suggest wiping system, data, cache and dalvik just for good measure. If she wants to keep a lot of the apps' progress/settings she has, I would install Titanium Backup and back up all user apps first before doing anything. She may have everything synced with her Google account as I believe you can sync apps and their data through Google now, but I haven't tested it yet.
To install the ROM, you'd just need to put it somewhere locally on your tablet, I have a '000Flash' folder on the root of my internal SD storage for any ROMs/kernels/modems (on my phone), etc. Place it in there, then get yourself into recovery. Once in recovery, wipe everything I mentioned above, then go back to the install/flash option of whatever recovery you're using. Flash the .zip file you just downloaded and put locally on your tab. Wait a few minutes and boot her up!
Just make sure you have the right software for the right version tablet you have, N5110 vs N5100.
Click to expand...
Click to collapse
Thank you very much, the same as I am use to really. I do have my system backed up, as well as Titanium Back UP for apps and data. So should be fine. I do have the N5110
BobC43 said:
Thank you very much, the same as I am use to really. I do have my system backed up, as well as Titanium Back UP for apps and data. So should be fine. I do have the N5110
Click to expand...
Click to collapse
No problem, shouldn't be too different than what you're already used to, but I can understand the need for clarification when it comes to different devices as they're all a little bit different.
OK, on 4.2.2, no problems at all after I found how to turn debugging mode on. THAT IS STRANGE
BobC43 said:
OK, on 4.2.2, no problems at all after I found how to turn debugging mode on. THAT IS STRANGE
Click to expand...
Click to collapse
Hello!
Can you please share how to turn on debugging mode? Thank you in avdavauce!
Sent from my GT-N5110 using xda premium
gqinside said:
Hello!
Can you please share how to turn on debugging mode? Thank you in avdavauce!
Sent from my GT-N5110 using xda premium
Click to expand...
Click to collapse
Settings / About Device /
Then tap the build number 7 times. As you are getting close to 7 taps, the screen will tell you how many more till you are in development.
BobC43 said:
Thank you very much, the same as I am use to really. I do have my system backed up, as well as Titanium Back UP for apps and data. So should be fine. I do have the N5110
Click to expand...
Click to collapse
Also you will need to have CWM or TWRP installed as a custom recovery for it to work. There are plenty of options for installing and the new versions that are non touch should fix any issues uyou had previously. Happy flashing!
Sent from my GT-N5110 using XDA Premium HD app
Yo Nate Dogg!!!!
I am Here!
Now we can get Jammin on this one too!!!!
I will be Flashing this on Friday, Looking around the hood now just seeing what is what on this Note 8!
Get some of that fly a$$ **** from the Note 2 over here! lol
Piece my brotha!
See you soon!
~B
@beanstown106
I'm all rooted and running the ROM...
This ROM definitely needs a little TLC...
How about putting a list of requests together so maybe we have an Idea of what we can expect?
Here is a thread for customizing this ROM!!!
Here is a link to the Google Edition 4.3 Camera
This works I have it installed. and it is pretty sweet. (even on a 5mp Camera)
I installed xposed framework today and it works well on this ROM. Has anyone else tried this?
You can go here for other mods to add to it...
After you have the Xposed frame work installed you can install the app_settings see attachments, to modify the per app DPI settings.
example, you open up app settings go to gmail, set the dpi to 160 & screen (dp): 1000x1600
I did this for System settings as well and they look nice.
Play around with it and we can build on it...
You can find other mods that you can see if they work and build a list in a new thread. REMEMBER TO BACK UP FIRST!
Ge the disabler in attachments to flash in case you get into a boot loop. These work well since this is a stock ROM.
NottachXposed works very nicely for this ROM... You just have to play with it a little bit, but you can tweak it out nicely...
Don't forget to grab the Multi-Window Manager over in the Themes and app section. It works Great Without any flaws so far...!
If you need a 3-way reboot menu, here is an excellent app here for that...
Knock it Off Please
OK, please stop with all the "bad-mouthing" and "trolling" and... the "Off-Topic" posts. You know the rules, especially in the Dev Forum.
You wanna post garbage or talk about who's gonna do what, then go to the main Android "Off Topic" forum.
Thread cleaned. (please don't make me come back in here again)
MD
Thanks for the deodexed, recovery flashable rom. I just flashed it and got everything set up. So far everything is running great.
Sent from my GT-N5110 using Xparent Green Tapatalk 2
Hi all! I am presently using Validus rom - 4.4.4 kitkat. Today, not sure if it an update that caused it, but I keep on getting "android.systemui has stopped" and it prevents me from working. As a result of this, I am thinking of trying out another rom. Any suggestions?
Idowu said:
Hi all! I am presently using Validus rom - 4.4.4 kitkat. Today, not sure if it an update that caused it, but I keep on getting "android.systemui has stopped" and it prevents me from working. As a result of this, I am thinking of trying out another rom. Any suggestions?
Click to expand...
Click to collapse
Plenty to choose from and you are obviously welcome to try any. You would be the first to run into that.
Did you flash clean?
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Sent from my SAMSUNG-SGH-I717 using XDA Free mobile app
I did wipe the cache through recovery mode & reflashed gapps but the problem persisted and was resolved by removing the google account from settings and signing again into google account.
As an excuse, I actually decided to try out another rom and wanted suggestions from the array of options
Idowu said:
Sent from my SAMSUNG-SGH-I717 using XDA Free mobile app
I did wipe the cache through recovery mode & reflashed gapps but the problem persisted and was resolved by removing the google account from settings and signing again into google account.
As an excuse, I actually decided to try out another rom and wanted suggestions from the array of options
Click to expand...
Click to collapse
Many will not make those suggestions as it tends to pit one persons work against another. Also what works great on one device will or may not work the same on another. That is why you are encouraged to try many and depending on what kind of user you are, you may benefit from some more than others.
Hint: look into roms that have been around for a while. Post count will help you there. Start reading from the back of thread which will tell you the most recent issues folks may have been having. If you dont like the issue, or there is no solution, dont flash and move on.
Another hint on the cleanliness of a flash.
Factory wipe 3 time
Flash rom
Flash rom again as 2 different flashes can produce 2 different results.
Flash gapps
Wipe Davlik and Cache
Boot up and let sit 10 or so
Reboot and set up
That is as clean as you can get. System UI failure is common with dirty flash. Get all those file reminents out of there.
Have fun
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
captemo said:
Many will not make those suggestions as it tends to pit one persons work against another. Also what works great on one device will or may not work the same on another. That is why you are encouraged to try many and depending on what kind of user you are, you may benefit from some more than others.
Hint: look into roms that have been around for a while. Post count will help you there. Start reading from the back of thread which will tell you the most recent issues folks may have been having. If you dont like the issue, or there is no solution, dont flash and move on.
Another hint on the cleanliness of a flash.
Factory wipe 3 time
Flash rom
Flash rom again as 2 different flashes can produce 2 different results.
Flash gapps
Wipe Davlik and Cache
Boot up and let sit 10 or so
Reboot and set up
That is as clean as you can get. System UI failure is common with dirty flash. Get all those file reminents out of there.
Have fun
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks a lot for the tips!
T Sen t from my SAMSUNG-SGH-I717 using XDA Free mobile app
captemo said:
Many will not make those suggestions as it tends to pit one persons work against another. Also what works great on one device will or may not work the same on another. That is why you are encouraged to try many and depending on what kind of user you are, you may benefit from some more than others.
Hint: look into roms that have been around for a while. Post count will help you there. Start reading from the back of thread which will tell you the most recent issues folks may have been having. If you dont like the issue, or there is no solution, dont flash and move on.
Another hint on the cleanliness of a flash.
Factory wipe 3 time
Flash rom
Flash rom again as 2 different flashes can produce 2 different results.
Flash gapps
Wipe Davlik and Cache
Boot up and let sit 10 or so
Reboot and set up
That is as clean as you can get. System UI failure is common with dirty flash. Get all those file reminents out of there.
Have fun
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
I am back to having system UI failure. The problem came up after the automatic update of google play.
Now, the systemui failure has dissapeared after I re-flashed the Validus rom through the recovery mode. But the google play services are not working. The last time I was able to get all back to "normal" by also re-flashing gapss.
If I re-flash gapps, I guess I will have to remove the google account and re-sign in. But after another automatic update to google play services, I will be back to the system UI failure.
The options I see are:
1. Do a backup of my data and clean flash as suggested by Captemo. I think this is the best option.
2. Do option 1 but do not flash gapss. I read in a Security thread http://forum.xda-developers.com/general/security/security-android-security-conscious-mind-t2835412 about going with custom rom + nogapps. But then how do one use the google services - especially google play?
3. Do what I have done so far: no factory reset et al, reflash Validus, reflash gapps, remove google account and re-signin. And then prevent automatic update to google services; how can this be done - preventing automatic update to google play services?
Thanks
I have the same systemui loop problem
Don't bother with "clean" flash, it won't help with Validus rom. I did exact steps as suggested by Captemo. But when I'm updating Google+ to version Aug 12, I'm immediately getting com.android.systemui error loop. It's not completely fatal, could be fixed by wiping cache, dalvik, and data in recovery, and flashing previous version of Google apps. But in that case you will lose all other installed apps of course. In Google Play options you can disable automatic update of applications, and just ignore updates (for me it's only Google+, for example YouTube update is ok).
I like Validus rom, it's quite good, but not compatible with Google+ app somehow.
UPDATE: in Validus 6.1 this com.android.systemui error loop is FIXED! I have all Google applications up to date now.
Used "MINI MODULAR PACKAGE" from http://forum.xda-developers.com/showthread.php?t=2397942
Idowu said:
I am back to having system UI failure. The problem came up after the automatic update of google play.
Now, the systemui failure has dissapeared after I re-flashed the Validus rom through the recovery mode. But the google play services are not working. The last time I was able to get all back to "normal" by also re-flashing gapss.
If I re-flash gapps, I guess I will have to remove the google account and re-sign in. But after another automatic update to google play services, I will be back to the system UI failure.
The options I see are:
1. Do a backup of my data and clean flash as suggested by Captemo. I think this is the best option.
2. Do option 1 but do not flash gapss. I read in a Security thread http://forum.xda-developers.com/general/security/security-android-security-conscious-mind-t2835412 about going with custom rom + nogapps. But then how do one use the google services - especially google play?
3. Do what I have done so far: no factory reset et al, reflash Validus, reflash gapps, remove google account and re-signin. And then prevent automatic update to google services; how can this be done - preventing automatic update to google play services?
Thanks
Click to expand...
Click to collapse