yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab  Android Development] stimpz0r:
first off - im going to say this once more. AOKP BUILD #39 IS

NOT THIS ROM

, i dont support official builds of AOKP, so if you try to install them i cant help you. the only build i will help you with is the one downloaded from the first post. THIS IS NOT AN OFFICIAL AOKP SUPPORT THREAD.

BUT i do want to resolve the issues with CDMA for my build (not that i have any idea what exactly they are). you need to give as much detail as possible:

how are you restocking?

what are you using to restock?

where did you download the rom you are restocking from?

what EXACTLY are the errors / behaviour you get when it isnt working

list the steps you take to restock and install STEP BY STEP

and the holy grail of information to help your cause:

logcat or last_kmsg log (and yes they are available in bootloop situations)

you cant prevent a bootloop from happening by holding vol up, that is only to get you into recovery mode. if that doesnt work then its a kernel issue.

remember, this is a majority GSM thread, and because of that 98% of people dont have any idea about CDMA or the steps to take. if you dont give us as much information as possible, no one is going to be able to help you.

read the reply above and fill in the blanks, and someone here (maybe even me) will help you. you are running a tablet that is different to the majority of users tablets, therefore to get help you need a little more (a lot more) information than "im getting a bootloop". perhaps then you will get a straight answer.

im not sure about backlight notifications to be honest, i turn off the backlights because they always bothered me at night so i never see them. the way to stop the backlight from turning off when the screen is on is to go to ROMControl ->Tablet Tweaks -> Backlight Timeout -> set to Never
[Galaxy Tab  Android Development] priyana:
Hey! I never suspect back light time out set to Never means always off.

I thought it meant never timeout , alias always on :-)
[Galaxy Tab  Android Development] jlvlawrence:
I'd be happy to help. In the link that I provided in my first post, there is a link that for a zip that includes heimdall, kernel, and clockwork. I unzipped it and flashed the kernel and recovery through odin. I believe it's cwm5x. After I flashed those the tab booted up but acted weird. I was able to get it into cwm though. I then flashed cm9 nightly and the tab booted up after that flash. I then went back into cwm and flashed gapps. I have flashed the two most recent cm9 nightlies. I just wiped the cache between nightlies like I do with my xoom.
[Galaxy Tab  Android Development] pdppdp:
Does any one know what line crossing wifi signal? Can't switch wifi on and off because of that line.
[Galaxy Tab  Android Development] salahmed:
I don't what is this line, but can you try wiping dalvic cache then reboot, may be this will solve the issue, by the way did changed the DPI LCD density???
[Galaxy Tab  Android Development] pdppdp:
No. I didn't change anything.

I'll try cleaning dalvik and will report.
[Galaxy Tab  Android Development] AZImmortal:
Thanks for the tip. After changing the backlight timeout to never, I think it enabled backlight notifications so I think it's already baked into the kernel. I have two other questions that are probably related to each other.

1. Is there a way to get the notification area to show the "plus" icon that means that there are more notifications than can be displayed? Unless there's a setting that I'm missing, there's no way to tell when I have more notifications than those displayed without opening the notification drawer.

2. Is there a way to disable the on-screen buttons and move the notification area to the left side? I'm guessing that the placement of the notification area is related to the inability to show the "plus" icon. I use the capacitive buttons (as you can tell) so I'd rather have a larger notification area.

Thanks for the great ROM. Other than these issues, the performance and experience of this ROM is making me regret not switching sooner. :)
[Galaxy Tab  Android Development] hellot1M:
i said real life boot loop lol. I gave you all the information I had. The tab is stock. Its Cdma. Its Verizon not sprint. And I'm wanting to try aokp. Guides point to either gsm and the ones that are for sprint it seems Verizon users are having issues. There are several different methods with some having better luck with one over the other.

Thank you! I'll try this and report back.
[Galaxy Tab  Android Development] hellot1M:
Ok I think I'm in a install loop.... it keeps rebooting, going to aokp sgt7, then Samsung, then a quick flash of the cwm screen then the process starts over........

Edit: I can turn off the device but when I turn it back on it goes back to the installing loop... what do I do :(
[Galaxy Tab  Android Development] yosup:
AFAIK, it's not possible to completely disable the nav bar buttons.

To move notification area to left side:

* ROM Control » Tablet Tweaks » [x] Mirror Status Bar

To minimize & "hide" the nav bar buttons from view (just a wild suggestion) ...

ROM Control » Navigation Bar settings:

* Navigation Button Quantity = ( set to just 1 ).

* Navigation Bar Buttons » Button 1 Action & Icon = ( set to "menu" ).

* Advanced Settings » Nav Button Transparency = ( set it to "0%" ).

. - or ... change the Nav Bar Color to match the background (ie. black).
[Galaxy Tab  Android Development] Neckhole:
Thanks for being willing to work with us CDMA users! We appreciate it.

I've got a stock image that I've been flashing via Odin back to my Sprint Galaxy Tab. The exact directions and what I've done are posted on the forums in a post on these forums. There's also a bunch of information in the [SPRINT][CDMA]Galaxy Tab (SPH-P100) Mega Development Starter Thread (CWM, EF17 TAR) thread.

However, when trying to work through the steps to flash this ROM, I was getting script assert errors:

-- Installing: /sdcard/aokp_p1c_build-38.zip
Finding update package...
I:Update location: /sdcard/aokp_p1c_build-38.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "galaxytab7c" || getprop("ro.build.product") == "galaxytab7c" ||
getprop("ro.product.device") == "p1c" || getprop("ro.build.product") == "p1c" ||
getprop("ro.product.device") == "SCH-I800" || getprop("ro.build.product") == "SCH-I800" ||
getprop("ro.product.device") == "SPH-P100" || getprop("ro.build.product") == "SPH-P100" ||
getprop("ro.product.device") == "vzwtab" || getprop("ro.build.product") == "vzwtab"
assert failed: getprop("ro.product.device") == "galaxytab7c" || getprop("ro.build.product") == "galaxytab7c" || getprop("ro.product.device") == "p1c" || getprop("ro.build.product") == "p1c" || getprop("ro.product.device") == "SCH-I800" || getprop("ro.build.product") == "SCH-I800" || getprop("ro.product.device") == "SPH-P100" || getprop("ro.build.product") == "SPH-P100" || getprop("ro.product.device") == "vzwtab" || getprop("ro.build.product") == "vzwtab"
E:Error in /sdcard/aokp_p1c_build-38.zip
(Status 7)
Installation aborted.

Thanks to priyana, we tied it back to the fact that the ClockWorkMod Recovery that comes with the Sprint Tab ROMs I referenced earlier are older (4.0.1.5). There's a thread on RootzWiki which helps you flash a newer version of CWM (5.0.2.7).

After that, I was able to flash the ROM (aokp_p1c_build38.zip) without getting any more script assert errors. However, my device started bootlooping after that and I couldn't get it to go back into Recovery. I only could get it back into download mode. In Download mode, I was able to re-flash back to stock with Odin and that's the state the Tab is currently in.

Later on (maybe tonight after work, not sure), I will try and repeat the process and grab a logcat to share.
[Galaxy Tab  Android Development] hellot1M:
That's exactly what mine is doing. As long as I'm not the only one lol.
[Galaxy Tab  Android Development] greatdaneduke:
I understood your initial post regarding AOKP. The reason I mentioned build 39 is because your rom and AOKP build 39 causes a boot loop after install. Thank you for responding.
[Galaxy Tab  Android Development] hellot1M:
OK I have nightly cm9 flashed and working. I'm on it now. Could I flash this over cm9 without running into the boot loop from flashing over gb. It seems this had a problem converting to mtd but now that cm9 converted successfully kang should flash without having to go through the process right?
[Galaxy Tab  Android Development] TarKin:
heating problem

good evening,

i tried to read most of the thread, but did not really find a solution for this one (and neither an explanation).

the thing is: i was using the stock rom and overcome (every rom + kernel) for months without problems. my tab did not even slightly heat up, also no while watching hd movies or using it as navi in my car.

so the thing is: i think the current aokp port is amazing. its fast, nearly bugless, very nice to use. big thanks for that one.

*but*

why on earth does it heat up so much? even with only a bit of music playing or browsing (no flash) sites ...its getting very hot.

is the problem for that known? and if so: is someone working on it?

thanks for everyone who can enlighten me on that one.
[Galaxy Tab  Android Development] AZImmortal:
Thanks for the suggestions, but I didn't to just want to move the notification area to the left in this way but rather expand the notification area to run across the length of the screen starting from the left with the clock/wifi icon/battery icon/etc on the right, like this picture but with the status bar on the bottom of the screen (I'm assuming this would be the "normal" ICS status bar layout?).
[Galaxy Tab  Android Development] yappoe:
This is a "normal" ICS status bar layout for Phone. default AOKP SGT7 is set for tablet layout. If you want a phone layout, (status bar on the top across) you can set the LCD Density to 240dpi.

System Settings > Rom Control > General UI > LCD Density

Sorry, you can't get status bar on the top AND tablet layout (at least not now).

---------- Post added at 10:45 AM ---------- Previous post was at 10:28 AM ----------

Hey Priyana, I notice this too, and I think what's happening is (I'm hoping you can confirm it too):

When I left my G-tab charging over night, I would get about 10% deep sleep and about 60%-70% at 200MHz. But after I left my tab uncharged and unused during the day, the deep sleep statistics increases to about 30-40%.

So I reset the CPU spy before each scenario, and I got 70+% in 200MHz with overnight charging, and I got 60+% in deep sleep when I leave the Tab uncharged overnight.

But if this is correct, it should not affect battery consumption. It may affect charging speed though.
[Galaxy Tab  Android Development] AZImmortal:
You've misunderstood what I'm asking for. I don't want the status bar on top. I want it on the bottom but without the nav bar and with the notification area on the left side while the clock and related icons stay on the right side.
[Galaxy Tab  Android Development] yappoe:
@AZImmortal: then yosup's suggestion is the closest you can get from what you'd like to have, I guess. Otherwise, I don't think it's possible to set it the way you want exactly.
[Galaxy Tab  Android Development] priyana:
I haven't been able to get any deep sleep whatsoever. I had reset the CPU Spy timer. Use the Battery Calibrator (which works well for me once in build 37).

My tab discharging on standby (airplane mode, wifi off) at around 5% per hour.

BatterBatteryStat app shows kernel wakelock taken by "svnet".

My next step will be to flash boot.img from build #37 and see how it goes.

I am quite sure I did nothing different in #37 and #38, no new apps either.
[Galaxy Tab  Android Development] yappoe:
I guess we have different problems. One of those hard to replicate performance bugs that any developer would hate to see/hear.
[Galaxy Tab  Android Development] pdppdp:
Wiping dalvik cache didn't solve the problem. Battery bar is not activated. Anyone else?
[Galaxy Tab  Android Development] linux150:
Hi !

Does USB Host work on this ROM ?

When i connect an USB Stick it doesnt work ?!

I want to try DSLR Remote but it says "no device connected"

On the device list there is the galaxy tab, but as i said it doesnt work.

Any settings to do on the rom ?

lg

linux150
[Galaxy Tab  Android Development] gwbard:
try Rom Control / Toggles / Brightness location = set to On top
[Galaxy Tab  Android Development] stimpz0r:
ok before i start replying, fair warning - this is gonna be a big one! :D

i will try to group relevant posts together, so dont freak out about them being in an incorrect order.

wow! excellent work on the detail in these two posts. not only have you helped me better understand your situation, but you have also given people a basis for installing on their Sprint tabs.

when you got stuck in the bootloop (the one where you saw the recovery screen flash up), you need to wait until it power cycles (i.e. screen turns off), then hold down vol up until it goes into recovery. holding it down the whole time probably wouldn't work.

the recovery log you posted was from the previous build you had installed before you flashed AOKP (ro.modversion is a dead giveaway there) but if you look at the filesystem table too, you will see that most partitions are either rfs or bml (which means not mtd) so unfortunately this wont work.

@ALL CDMA USERS:

i need a willing guinea pig (test subject) here - if you get a bootloop at the same point as Neckhole after flashing AOKP and:

have a spare 5 minutes

are willing to download the latest official sgt7 cdma official cm9 build (get it from here)

have a working copy and knowledge of how to use heimdall in command line mode OR have winzip and can add the new kernel to the rom zip

then do the following steps:

get the tablet to the point where it bootloops

open the downloaded zip file of the latest cm9 cdma build and extract the boot.img file

go to your command line / terminal and run the following in the directory you extracted the boot.img: heimdall flash --kernel boot.img --recovery boot.img

then please report back your findings on this procedure. this will install a more vanilla kernel (not the cutting edge variant), but a known working kernel for vzw cdma tablets (that should work with sprint too). this will tell me whether the kernel is the problem or not.

you should be fine flashing it over cm9, but keep your cm9 zip on your tablet just incase it doesnt...

read the response i wrote to Neckhole above and try that (flashing the new kernel), if the cm9 kernel works better i will go back to using the cm9 source and releasing a flashable humberos kernel along with it.

the three posts above all point to issues with the kernel. according to HumberOS and his github a lot of these problems should / could be fixed in the next AOKP release (i.e. when i pull down the recent changes),
[Galaxy Tab  Android Development] pdppdp:
That's the solution. Thank you. :thumbup:
[Galaxy Tab  Android Development] Neckhole:
What I lack in experience, I make up for in verbosity! When the time comes, you can use these steps in your installation directions for other Sprint users.

IIRC, I definitely held it down when it power cycled. I want to say it did that the first time, then went into the boot loop. That power cycle happened pretty quickly and I've slept since I did it, so I can't say for certain that I caught it in time.

This makes perfect sense, I thought it was a long shot. I was hoping somehow I could extract some useful log info for you. Maybe next time!

I'll try this all again sometime this weekend (flash back to stock, flash CWM, flash SGT7 AOKP and get it into a boot loop). I'm more used to the Heimdall front-end, but no stranger to a command line.

If it helps at all, I flashed a CM9 nightly that someone posted about it in the General Forums ( [HOLY CRAP][SPRINT P100] Stock to ICS - Complete Walkthrough) and that's working right now on my tablet.

For fun, I did try and flash the SGT7 AOKP on top of that CM9, and that didn't work out so well. The tablet was hanging on the Samsung screen.

At any rate, I'll reply back again with my results when I get some time to look at it this weekend.

Thanks for the responses, I'm a more than willing guinea pig! Is there anyone else with a Sprint Tab want to help us out?
[Galaxy Tab  Android Development] Bad2hold:
No issues, all fine, great work guys. Even better than the supported HTC sensation aokp which has lots of bugs still.

Just one question: Is *wifi direct* supposed to work?

Able to find it with other devices when turned on but no connection.

Or is it more a matter of hardware? Would be great to know..

Thanx so far!
[Galaxy Tab  Android Development] yosup:
BUILD #40

AOKP / Roman just anounced it, but the official changelog hasn't been posted yet. I'll post more info once it becomes available.

Here's the messy version if anyone's interested:

http://pastebin.com/sQhqzw5p

Based on a quickie skim of the text, hopefully this one helps those users who kept getting bootloops:
[Galaxy Tab  Android Development] salahmed:
Thanks for the news update. So it is build 40 and may be the next one will be milestone 6, I got headache and took 2 Panadol tablets :D when I had read this change log, as roman wrote he will make this more organized because it look so messy.
[Galaxy Tab  Android Development] yosup:
LOL. Acetaminophen always helps alleviate those pesky headaches brought on by messy changelogs. :rolleyes:

MS #4 = 3/8/12

MS #5 = 4/28/12

You're probably right that we're getting very close to another Milestone. :cool:
[Galaxy Tab  Android Development] gildow:
Actually kind of glad that we missed build 39 for our SGT7...I'm using build 39 on my SGS..and boy..hell lots of issue.... :p Even after with device wipe!!
[Galaxy Tab  Android Development] yosup:
@E1:

BUILD #40 ... anounced by AOKP:

* http://aokp.co/index.php/releases/_/build-40-r26

* AOKP does NOT directly provide official GSM builds

* p1c = Verizon / CDMA ... ( NOT GSM )
[Galaxy Tab  Android Development] droiduzr2:
What does fix tablets mean?
[Galaxy Tab  Android Development] yosup:
Probably "fix bootloops on tablets" mentioned in that pastebin link (ie. full changelog).
[Galaxy Tab  Android Development] priyana:
Hi Stimpz0r,

FYI, I have flashed humberos latest kernel of 20120624 compiled by alroger. Only a few hours so I don't know what I will get.

There is 1300Mhz setting.

Battle drain seems to have improved a little but not much, I will see how overnight. Still no deepsleep triggered for me so far. :(
[Galaxy Tab  Android Development] humberos:
The kernel has updated.

Deep Sleep works fine here.
[Galaxy Tab  Android Development] dabrowsk:
From where can I download this kernel?
[Galaxy Tab  Android Development] 123Kage:
Can i flash this kernel in my AOKP 38th build with Odin. Sorry if my question is so funny for all of you. I just learn how to flash custom ROM.
[Galaxy Tab  Android Development] priyana:
Even better.

OsitKP at the TE4M/Kangs discussion thread made a CWM flashable one

http://xdaforums.com/showpost.php?p=27858742&postcount=1780

I have not tested this way, but should work.

---------- Post added at 09:26 AM ---------- Previous post was at 09:23 AM ----------

Humberto,

Thanks. It is just mine. Overnight still not deepsleeping, and BetterBatteryStats shows "svnet" is the kernel wakelock.

Not sure what sort of network service preventing it frol sleeping.

Later I will probably do a data wipe and start with clean build #38 and your kernel only.

Now I just wipe /cache and dalvik cache first and see.

Edit: Yup, a clean wipe one shows deepsleep happening. Back to hunting gremlins.

Cheers.
[Galaxy Tab  Android Development] gildow:
Hi Humberos,

Been a while...hope you are good!

Anyway..where can I get your kernel?

Cheers!
[Galaxy Tab  Android Development] stimpz0r:
and this shall be released, working on something else (kinda to do with the builds) then i will sync up properly... stay tuned ;)

there was an issue with the lockscreen layout for music controls (i believe) that was causing a bootloop on tablets (well android would crash upon boot) - so it was probably lucky i didnt do an upgrade to build #39 ;)

hello HumberOS, nice of you to drop by! :D

only some people were suffering the no deep sleep issue, and i wasnt one of them so i cant comment on why it happens or what it causes. but your new release might have fixed it too!

i still have had no positive feedback on cdma kernels though (only mention of bootloops), so i might have to go back to jt's cdma kernel for the cdma builds until i can get some positive feedback that it is working.
[Galaxy Tab  Android Development] fedefurious2:
no link to the kernel v5? all link remaind me error 404..
[Galaxy Tab  Android Development] droiduzr2:
Is build 40 ready yet? :laugh::laugh::laugh:
[Galaxy Tab  Android Development] Arios_tab:
I heard about the 40Build come out already ?
[Galaxy Tab  Android Development] MiCmAsTa:
Deep sleep FTW!
[Galaxy Tab  Android Development] priyana:
You heard wrongly.

If it is not here it is not here.

Maybe you are thinking of official AOKP or the other P1000 build in this forum.

But definitely not Stimpz0r one.
[Galaxy Tab  Android Development] humberos:
Hey dude!

I will check CDMA variant (kernel sources) one more time.

Thank you!

Greetings from Brazil!
[Galaxy Tab  Android Development] 123Kage:
Great now kernel is updated through CWM. Using live OC 120% CPU 1300 and very stable so far.

Thanks :)
[Galaxy Tab  Android Development] agustincordoba:
Hi, the only time my Tab does not enter deep sleep is when it is charging.

Enviado desde P1000 con Tapatalk

Sent from P1000 via Tapatalk
[Galaxy Tab  Android Development] Sequester:
I flashed the latest kernel of humberos and it seems that battery lasts slightly longer. But: the tablet goes into deep sleep but not like shown in the screenshots a few posts earlier. It mostly stays at 100 MHz. I have not made any additional changes and run a gsm model.

If any additional info is required pls let me know.

Gesendet von meinem GT-P1000 mit Tapatalk 2
[Galaxy Tab  Android Development] stimpz0r:
ok, build #40 IS on its way, though i have hit a minor bump in the road... seems ive broken something along the way, i still cant get p1l/p1n to build but if i try to build p1 it tries to do a p1n build and breaks on the OTA.

rest assured i will work through this and hopefully have it building by the end of the night. :fingers-crossed:

i am going to release the next cdma build with a jt kernel, but release a build of your cdma variant as a flashable (once i work out how to build a boot.img seperately again).

i was going to do the same for p1, but due to the below comment i think ill go back to your kernel for p1 and see how we roll ;)

good to see its working!

however, you aren't using LiveOC, its not enabled in the later kernels due to instability. its been re-enabled in ROMControl due to my nasty hack code disabling (yeah i was lazy and didnt factor in someone else flashing another kernel with it disabled). although it will allow you to click the settings and say its changed, its not actually doing anything.

thanks for the reminder though, i'll clean that up before i release. ;)
[Galaxy Tab  Android Development] linux150:
Hi !

Did anybody test this USB Host Controller ?

I did try,and it shows that USB Host is active, but it doesnt work with my camera ?!

I´m using only the OTG cable and not an Y-Cabel with Power Supply. Maybe thats the problem ?

Any solutions ?

lg

linux150
[Galaxy Tab  Android Development] asgari:
Try one of these methods, the tab does not provide enough power.